Skip to content

CI: upgrade weekly cron devdeps jobs to Python 3.15 (dev) - #20198

Draft
neutrinoceros wants to merge 1 commit into
astropy:mainfrom
neutrinoceros:ci/cp315
Draft

CI: upgrade weekly cron devdeps jobs to Python 3.15 (dev)#20198
neutrinoceros wants to merge 1 commit into
astropy:mainfrom
neutrinoceros:ci/cp315

Conversation

@neutrinoceros

Copy link
Copy Markdown
Contributor

Description

Fixes #20196

  • By checking this box, the PR author has requested that maintainers do NOT use the "Squash and Merge" button. Maintainers should respect this when possible; however, the final decision is at the discretion of the maintainer that merges the PR.

@github-actions

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Thank you for your contribution to Astropy! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.

  • Do the proposed changes actually accomplish desired goals?
  • Do the proposed changes follow the Astropy coding guidelines?
  • Are tests added/updated as required? If so, do they follow the Astropy testing guidelines?
  • Are docs added/updated as required? If so, do they follow the Astropy documentation guidelines?
  • Is rebase and/or squash necessary? If so, please provide the author with appropriate instructions. Also see instructions for rebase and squash.
  • Did the CI pass? If no, are the failures related? If you need to run daily and weekly cron jobs as part of the PR, please apply the "Extra CI" label. Codestyle issues can be fixed by the bot.
  • Is a change log needed? If yes, did the change log check pass? If no, add the "no-changelog-entry-needed" label. If this is a manual backport, use the "skip-changelog-checks" label unless special changelog handling is necessary.
  • Is this a big PR that makes a "What's new?" entry worthwhile and if so, is (1) a "what's new" entry included in this PR and (2) the "whatsnew-needed" label applied?
  • At the time of adding the milestone, if the milestone set requires a backport to release branch(es), apply the appropriate "backport-X.Y.x" label(s) before merge.

@neutrinoceros
neutrinoceros force-pushed the ci/cp315 branch 2 times, most recently from 5b2fd36 to ee123e2 Compare August 4, 2026 05:12
@neutrinoceros

Copy link
Copy Markdown
Contributor Author

I missed that these jobs were requiring matplotlib, which doesn't have wheels for 3.15 yet. I expect it to happen soon however, so I'm going to keep this PR around as a draft for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

TST: devdeps on weekly cron not installing numpy-dev

1 participant