Skip to content

Backport PR #18786 on branch v7.1.x (Add arm64 windows support) - #18793

Merged
pllim merged 1 commit into
astropy:v7.1.xfrom
pllim:backport-of-pr18786-onto-v7.1.x
Oct 28, 2025
Merged

Backport PR #18786 on branch v7.1.x (Add arm64 windows support)#18793
pllim merged 1 commit into
astropy:v7.1.xfrom
pllim:backport-of-pr18786-onto-v7.1.x

Conversation

@pllim

@pllim pllim commented Oct 28, 2025

Copy link
Copy Markdown
Member

Description

This pull request is to manually backport

  • 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.

@pllim
Backport of astropy#18786 onto v7.1.x
79758e5 
to add build for Windows ARM64.

Also backport the ignore added in astropy#18573
so devs do not accidentally check in pyi files when switching
branches locally.
@pllim pllim added this to the v7.1.2 milestone Oct 28, 2025
@pllim pllim added Windows build Manual Backport skip-changelog-checks Tells bot to skip changlog checks skip-basebranch-check Skip base branch check for direct backports labels Oct 28, 2025
@github-actions

github-actions Bot commented Oct 28, 2025

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.

@github-actions

github-actions Bot commented Oct 28, 2025

Copy link
Copy Markdown
Contributor

👋 Thank you for your draft pull request! Do you know that you can use [ci skip] or [skip ci] in your commit messages to skip running continuous integration tests until you are ready?

@pllim pllim added the Build all wheels Run all the wheel builds rather than just a selection label Oct 28, 2025
@pllim
pllim marked this pull request as ready for review October 28, 2025 18:34
@pllim
pllim merged commit 7118415 into astropy:v7.1.x Oct 28, 2025
4 checks passed
@pllim
pllim deleted the backport-of-pr18786-onto-v7.1.x branch October 28, 2025 18:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

Build all wheels Run all the wheel builds rather than just a selection build Manual Backport Release skip-basebranch-check Skip base branch check for direct backports skip-changelog-checks Tells bot to skip changlog checks Windows

Projects

None yet

Milestone

v7.1.2

Development

Successfully merging this pull request may close these issues.

1 participant

@pllim