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

chore: Version bumps and package naming in CI and README #9

Merged
merged 5 commits into from
Oct 24, 2024

Conversation

douglasdavis
Copy link
Contributor

@douglasdavis douglasdavis commented Oct 14, 2024

Opening as part of the ongoing effort with #1. This assumes dropping 3.7 and 3.8 (EOL) is green-lit. I don't know much about the CI setup here, but I'm happy to keep tinkering with it to get this across the line.

Copy link
Member

@davidhewitt davidhewitt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, this looks good to me! The remaining macOS and MSRV jobs can be fixed separately, I think.

Just spotted one more bit of renaming...

README.md Outdated Show resolved Hide resolved
@douglasdavis
Copy link
Contributor Author

Thanks, this looks good to me! The remaining macOS and MSRV jobs can be fixed separately, I think.

Just spotted one more bit of renaming...

Thanks! Will give it another parse later today.

douglasdavis and others added 2 commits October 21, 2024 20:47
@douglasdavis
Copy link
Contributor Author

douglasdavis commented Oct 22, 2024

Fixed a few more instances; there's still a small set of remaining links to the original repository's GitHub pages API docs, I think it's safe to fix some of those links after this fork has live API docs.

@cpu cpu mentioned this pull request Oct 22, 2024
@davidhewitt davidhewitt merged commit 4e18f54 into PyO3:main Oct 24, 2024
21 of 24 checks passed
@davidhewitt
Copy link
Member

Super, thanks!

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 this pull request may close these issues.

2 participants