Skip to content

feat(NODE-6932): Add Windows 11 + ARM64 to supported build hosts. #242

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

DanielRosenwasser
Copy link

@DanielRosenwasser DanielRosenwasser commented Apr 28, 2025

Description

What is changing?

This PR adds a runner for Windows 11 on ARM64. Currently the runner is in a preview state according to the docs on GitHub hosted runners; however, Windows ARM64 support currently has a gap.

Is there new documentation needed for these changes?

Other than in README.md, just in the changelog/HISTORY.md.

What is the motivation for this change?

Desire to support Windows+ARM64.

https://jira.mongodb.org/browse/NODE-6932

Release Highlight

Fill in title or leave empty for no highlight

Double check the following

  • Ran npm run check:lint script
  • Self-review completed using the steps outlined here
  • PR title follows the correct format: type(NODE-xxxx)[!]: description
    • Example: feat(NODE-1234)!: rewriting everything in coffeescript
  • Changes are covered by tests
  • New TODOs have a related JIRA ticket

@DanielRosenwasser DanielRosenwasser requested a review from a team as a code owner April 28, 2025 18:25
@DanielRosenwasser DanielRosenwasser changed the title Add Windows 11 + ARM64 to supported build hosts. feat(platform): Add Windows 11 + ARM64 to supported build hosts. Apr 28, 2025
@dariakp dariakp changed the title feat(platform): Add Windows 11 + ARM64 to supported build hosts. feat(NODE-6932): Add Windows 11 + ARM64 to supported build hosts. Apr 29, 2025
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.

2 participants