Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 1.1.0 onto PyPI #1230

Closed
johnthagen opened this issue Jan 12, 2025 · 12 comments · Fixed by #1232
Closed

Release 1.1.0 onto PyPI #1230

johnthagen opened this issue Jan 12, 2025 · 12 comments · Fixed by #1232

Comments

@johnthagen
Copy link
Contributor

johnthagen commented Jan 12, 2025

@cjolowicz @edgarrmondragon Could we tag and release a new version of nox-poetry onto PyPI? It's been 1.5 years since the last release, and it would be good to signal support for Python 3.12-3.13 and Poetry 2.0. This will also help signal that this project is still being maintained to potential new users.

It would be good to first merge

@edgarrmondragon
Copy link
Collaborator

I don't access to tagging new releases but it's a 👍 for me on publishing a new version to PyPI

@cjolowicz
Copy link
Owner

@edgarrmondragon @johnthagen Would you be happy to co-maintain this package?

@edgarrmondragon
Copy link
Collaborator

@edgarrmondragon @johnthagen Would you be happy to co-maintain this package?

Yeah, I'd be happy to help in any capacity 😄

@johnthagen
Copy link
Contributor Author

I also think @edgarrmondragon would be a great new co maintainer!

@cjolowicz
Copy link
Owner

Thank you @edgarrmondragon !

I invited you as a collaborator to this repository just now.

I can also invite you to Read the Docs, but I would need your Read the Docs username or email for that.

@johnthagen
Copy link
Contributor Author

@cjolowicz Should @edgarrmondragon also share his PyPI username so that he can publish new releases?

@cjolowicz
Copy link
Owner

@cjolowicz Should @edgarrmondragon also share his PyPI username so that he can publish new releases?

Yes happy to add @edgarrmondragon to PyPI . That said, GitHub workflows will take care of publishing, and that's the preferred way.

@johnthagen
Copy link
Contributor Author

That said, GitHub workflows will take care of publishing, and that's the preferred way.

Ah, good point!

@johnthagen
Copy link
Contributor Author

@edgarrmondragon Perhaps a good task would be merging or closing all of the open dependabot PRs? That way it's easier to track other PRs.

@edgarrmondragon
Copy link
Collaborator

I invited you as a collaborator to this repository just now.

Thanks!

I can also invite you to Read the Docs, but I would need your Read the Docs username or email for that.

That's edgarrm92.

@edgarrmondragon
Copy link
Collaborator

@edgarrmondragon Perhaps a good task would be merging or closing all of the open dependabot PRs? That way it's easier to track other PRs.

Yeah, a lot of those seem to be outdated. I'll start taking a look at them.

@cjolowicz
Copy link
Owner

I can also invite you to Read the Docs, but I would need your Read the Docs username or email for that.

That's edgarrm92.

Invite sent!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants