Skip to content

announce the NumPy 2.3.0 release #865

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

Merged
merged 1 commit into from
Jun 7, 2025

Conversation

charris
Copy link
Member

@charris charris commented Jun 7, 2025

Brief description of what is fixed or changed

Copy link

netlify bot commented Jun 7, 2025

Deploy Preview for numpy-org ready!

Name Link
🔨 Latest commit 47760ed
🔍 Latest deploy log https://app.netlify.com/projects/numpy-org/deploys/68445dd830342e00087aa9c3
😎 Deploy Preview https://deploy-preview-865--numpy-org.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@InessaPawson InessaPawson merged commit 554b3af into numpy:main Jun 7, 2025
4 checks passed
@InessaPawson
Copy link
Member

Thank you, @charris!

@mattip
Copy link
Member

mattip commented Jun 8, 2025

Is it something in my browser caching, I do not see the release on the front page but it is on the news page.

@charris do you want me to generate and upload documentation for 2.3?

@mattip
Copy link
Member

mattip commented Jun 8, 2025

See #866

@mattip
Copy link
Member

mattip commented Jun 8, 2025

It seems the directions might need more details visa-vis #866 to prevent this in the future?

@charris
Copy link
Member Author

charris commented Jun 8, 2025

do you want me to generate and upload documentation for 2.3?

Please do. Looks like the distutils problem is getting fixed, so maybe I can do it next time. I'd also appreciate if you updated RELEASE_WALKTHROUGH so I can get it right next time. Part of keeping it updated is to make it easier for the next release manager who comes along.

@melissawm
Copy link
Member

I've set up a github action to generate PDF docs for each release. I'd be happy to do the same for the html docs generation for each new release. This would stop requiring that someone builds it locally. Wdyt? Should I add it to the main repo or to numpy/docs?

https://github.com/melissawm/artoo/blob/main/.github/workflows/build_numpy_pdf.yml

@mattip
Copy link
Member

mattip commented Jun 9, 2025

I will go ahead and build the 2.3.0 docs but it makes sense to automate the docs building, even though it is a twice-a-year event. Could it use the existing requirement files?

@melissawm
Copy link
Member

Yes - I'll put something together. Cheers!

@mattip
Copy link
Member

mattip commented Jun 9, 2025

FWIW, the 2.3.0 docs are up, i also built and uploaded the pdfs.

@charris
Copy link
Member Author

charris commented Jun 9, 2025

Thanks Matti.

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.

4 participants