-
Notifications
You must be signed in to change notification settings - Fork 113
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
git-node: add release promotion step #402
base: main
Are you sure you want to change the base?
Conversation
b44d683
to
84b0a27
Compare
Codecov Report
@@ Coverage Diff @@
## master #402 +/- ##
=======================================
Coverage 76.34% 76.34%
=======================================
Files 21 21
Lines 1484 1484
=======================================
Hits 1133 1133
Misses 351 351 Continue to review full report at Codecov.
|
I'll review and try this when I do the 13.x release next week |
0666c26
to
13191bd
Compare
I'm trying |
Is it supposed to ask me for my GitHub credentials?
|
Okay, I found that I can enter my username/password/otp code and it continues.
|
The output of the next steps is weird:
|
Then it crashes on the secure tag step:
|
hmm @targos - it pulls information from your local ncu configuration 🤔 i have the normal setup for myself and it finds that i'm In re. the second issue - looks like And re. |
@codebytere yeah, I actually did not have my |
I wonder why it said that the PR does not have sufficient approvals. It has 6 of them 🤔 |
This is what is passed to
|
The branch switching doesn't work:
|
^ That's because |
if (!didResolveConflicts) { | ||
cli.warn(`Aborting release promotion for version ${version}`); | ||
return; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
else, we need to:
git add src/node_version.h # or ask the user to add conflicted files manually
git cherry-pick --continue
git push upstream master
git checkout branch-staging
The promotion step doesn't work. It stops immediately with a success message, but the promotion did not happen (note that the promotion script is interactive so we may have to run it in a special way) |
f6eee6a
to
946d16d
Compare
946d16d
to
d944859
Compare
Co-Authored-By: Michaël Zasso <[email protected]>
d944859
to
c1ab158
Compare
@targos rebased and updated a few things if you're willing to give this another spin on your next release! |
I'm giving it a try now with 12.17.0 |
0702242
to
3377b44
Compare
} else { | ||
if (!releasers.some(r => r.login === release.username)) { | ||
cli.stopSpinner( | ||
`${release.username} is not a Releaser; aborting release`); | ||
return; | ||
} | ||
cli.stopSpinner('Verified Releaser status'); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit:
} else { | |
if (!releasers.some(r => r.login === release.username)) { | |
cli.stopSpinner( | |
`${release.username} is not a Releaser; aborting release`); | |
return; | |
} | |
cli.stopSpinner('Verified Releaser status'); | |
} | |
} else if (releasers.every(r => r.login !== release.username)) { | |
cli.stopSpinner( | |
`${release.username} is not a Releaser; aborting release`); | |
return; | |
} | |
cli.stopSpinner('Verified Releaser status'); |
This PR is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made. |
This PR is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made. |
Refs #388.
Some of this hard to test, since it involved taking real steps that we take during releases.
I've chosen to seek active confirmation more here than in the prep stage, since many of the steps are irreversible, but I'm open to any and all thoughts about how much we might want.
This adds the secondary portion of release automation, for the promotion step. Specifically, we want to:
cc @nodejs/releasers