You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follow the rest of the checklist in the created issue.
node scripts/release-manager.js
1. Checkout the latest branch and reset deps
git checkout latest && git pull
node . run resetdeps
2. Pull in PRs
Search for PRs to merge. Some helpful gh searches:
gh pr list --draft=false --search "status:pending"
gh pr list --draft=false --search "status:success"
gh pr list --draft=false --search "review:required"
gh pr list --draft=false --search "review:approved"
Make sure the PR is targeting latest and not something else.
Make a judgment call to either squash or rebase the PR. Prefer using squash unless PR has multiple conventional commits.
Squash
gh pr merge -s <pr-num>&& git pull
Rebase
gh pr merge -m <pr-num>&& git pull
3. ❓ Optional: Update Deps
Steps
⚠️ This is an optional step, the way we are handling the dependencies now is to open then via Pull Requests so ideally any dependencies update that needs to go out in a release should have been merged already at this point. Refer to these steps in case there are important last-minute dependencies updates that needs to go out along with the current release.
Target Version: v8.15.1
Target Date: 2022-07-27
Created From:
Release-Process-(v8).md###Publishing the `cli`
0. Create
release-manager
issueFollow the rest of the checklist in the created issue.
1. Checkout the latest branch and reset deps
2. Pull in PRs
Search for PRs to merge. Some helpful
gh
searches:Make sure the PR is targeting
latest
and not something else.Make a judgment call to either squash or rebase the PR. Prefer using squash unless PR has multiple conventional commits.
Squash
Rebase
3. ❓ Optional: Update Deps
Steps
Check all deps
node . outdated
Check production deps
node . outdated -a --omit=dev
Install and commit each dep to a PR
Rebase-merge the PR if things look ok
Updating template-oss
node . i @npmcli/template-oss@latest -ws --include-workspace-root --save-exact
4. Make sure tests/lint pass
5. Generate Changelog
Push commits needed to generate the changelog
Write release notes to
CHANGELOG.md
Open
CHANGELOG.md
and check it for any unexpected/malformed entries.Commit
CHANGELOG.md
updates6. Update Version
node . version 8.15.1
7. Push to GitHub
Create a release branch in the remote repo
Create a PR with the body set to the manually formatted release notes from
CHANGELOG.md
Ensure PR CI checks pass
8. Publish Package
9. Update Dist Tag
❓ Optional: install via version to see how it runs locally before tagging
Set version to
latest
dist tagnode . dist-tag add npm@8.15.1 latest
10. Create a GitHub release
Create a GitHub release with the notes set to the body of the PR
11. ⏳ Temporary: Merge the release branch into
release-next
git checkout release-next git fetch && git pull git merge --ff-only latest git push origin release-next git checkout latest
12. Post on Twitter
13. Update Node.js
Sync our
npm/node
fork with thenodejs/node
upstreamTrigger the Create CLI Deps PR action (use the default input of
latest
)The text was updated successfully, but these errors were encountered: