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

feat(git-node): add release promotion step #835

Merged
merged 50 commits into from
Nov 13, 2024

Conversation

aduh95
Copy link
Contributor

@aduh95 aduh95 commented Jul 22, 2024

You can try it with git node release -S --promote https://github.com/nodejs/node/pull/53945.

Supersedes #402

/cc @nodejs/releasers

@targos
Copy link
Member

targos commented Oct 3, 2024

It is v20.x-staging, which is normal from my pov. I work on a v20.x release in my v20.x workspace

@aduh95
Copy link
Contributor Author

aduh95 commented Oct 4, 2024

It is v20.x-staging, which is normal from my pov

Does it need to be v20.x-staging for something else? Landing backport PR maybe? Asking because I'm wondering if we should rename it to defaultBranch to avoid the confusion – or if I choose just make an API call to get the name of the default branch (and assume there's a local branch with that name)

@targos
Copy link
Member

targos commented Oct 4, 2024

I believe it's for backport PRs, but I'm not sure.

@aduh95
Copy link
Contributor Author

aduh95 commented Oct 12, 2024

I've confirmed that to land a (backport or not) PR to a staging branch, NCU request you to set a different branch in your config. I've updated the promotion script to make an API call to get the name of the default branch instead of relying on the config.
I've also added a fallback when the version tag already exists to not crash if it points to the right commit and is correctly signed.

@aduh95
Copy link
Contributor Author

aduh95 commented Nov 13, 2024

I've tried it with the v18.20.5 release, and did not get any blocker. I'm tempted to land it, we might still want to iterate on it but I think it's at a point where we can rely on it. @nodejs/releasers, wdyt?

@targos
Copy link
Member

targos commented Nov 13, 2024

LGTM

RafaelGSS added a commit to RafaelGSS/node that referenced this pull request Nov 13, 2024
@aduh95 aduh95 merged commit dfa9c92 into nodejs:main Nov 13, 2024
10 of 11 checks passed
@aduh95 aduh95 deleted the git-node-release-promote branch November 13, 2024 14:07
nodejs-github-bot pushed a commit to nodejs/node that referenced this pull request Nov 19, 2024
Refs: nodejs/node-core-utils#835
PR-URL: #55835
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
tpoisseau pushed a commit to tpoisseau/node that referenced this pull request Nov 21, 2024
Ceres6 pushed a commit to Ceres6/node that referenced this pull request Nov 26, 2024
aduh95 pushed a commit to nodejs/node that referenced this pull request Nov 26, 2024
aduh95 pushed a commit to nodejs/node that referenced this pull request Dec 10, 2024
ruyadorno pushed a commit to nodejs/node that referenced this pull request Jan 5, 2025
marco-ippolito pushed a commit to nodejs/node that referenced this pull request Jan 22, 2025
marco-ippolito pushed a commit to nodejs/node that referenced this pull request Jan 22, 2025
marco-ippolito pushed a commit to nodejs/node that referenced this pull request Jan 22, 2025
marco-ippolito pushed a commit to nodejs/node that referenced this pull request Jan 24, 2025
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.

6 participants