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.

Sign up for GitHub

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

Jump to bottom

chore: release 9.3.0 #5974

Merged
merged 1 commit into from
Jan 12, 2023
Merged

chore: release 9.3.0 #5974

merged 1 commit into from
Jan 12, 2023

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Dec 17, 2022 •
edited
Loading

🤖 I have created a release beep boop

9.3.0

9.3.0 (2023-01-12)

Features

Bug Fixes

Documentation

Dependencies

arborist: 6.1.6

6.1.6 (2023-01-12)

Bug Fixes

config: 6.1.1

6.1.1 (2023-01-12)

Bug Fixes

libnpmdiff: 5.0.7

5.0.7 (2023-01-12)

Dependencies

libnpmexec: 5.0.7

5.0.7 (2023-01-12)

Dependencies

libnpmfund: 4.0.7

4.0.7 (2023-01-12)

Dependencies

libnpmpack: 5.0.7

5.0.7 (2023-01-12)

Dependencies

This PR was generated with Release Please. See documentation.

@github-actions github-actions bot requested a review from a team as a code owner December 17, 2022 03:33
@github-actions
Copy link
Contributor Author

github-actions bot commented Dec 17, 2022 •
edited by lukekarrys
Loading

Release Manager

Release workflow run: https://github.com/npm/cli/actions/runs/3904834260

Force CI to Update This Release

This PR will be updated and CI will run for every non-chore: commit that is pushed to latest. To force CI to update this PR, run this command:

gh workflow run release.yml -r latest

Release Checklist for v9.3.0

  • 1. Checkout the release branch

    Ensure git status is not dirty on this branch after resetting deps. If it is, then something is probably wrong with the automated release process.

    gh pr checkout 5974 --force
node . run resetdeps
node scripts/git-dirty.js

  • 2. Check CI status

    gh pr checks --watch

  • 3. Publish the CLI

    Warning:
    This will publish all updated workspaces, and will publish the CLI with the dist-tag set to next-9.

    Note:
    The --test argument can optionally be omitted to run the publish process without running any tests locally.

    node scripts/publish.js --test

  • 4. Optionally install and test [email protected] locally

    npm i -g [email protected]
npm --version
npm whoami
npm help install
# etc

  • 5. Set latest dist-tag to newly published version

    Warning:
    NOT FOR PRERELEASE: Do not run this step for prereleases or if 9 is not being set to latest.

    node . dist-tag add [email protected] latest

  • 6. Merge release PR

    gh pr merge --rebase
git checkout latest
git fetch
git reset --hard origin/latest
node . run resetdeps

  • 7. Check For Release Tags

    Release Please will run on the just pushed release commit and create GitHub releases and tags for each package.

    gh run watch `gh run list -w release -L 1 --json databaseId -q ".[0].databaseId"`

  • 8. Post on Twitter

    New @npmjs release: 9.3.0!

https://github.com/npm/cli/releases/tag/v9.3.0

Release details...

  • 9. Trigger docs.npmjs.com update

    gh workflow run update-cli.yml --repo npm/documentation

  • 10. Open nodejs/node PR to update npm to latest

    Warning:
    You must wait for CI to create the release tags before running this step.

    Trigger the Create Node PR action. This will open a PR on nodejs/node to the main branch.

    Note:
    The resulting PR may need to be labelled if it is not intended to land on old Node versions.

    gh repo sync npm/node --source nodejs/node --force
gh workflow run create-node-pr.yml -f spec=next-9

    If the PR should be opened on a different branch (such as when doing backports) then run it with -f branch=<BRANCH_NAME>. There is also a shortcut to target a specific Node version by specifying a major version number with -f branch=18 (or similar).

    # This will create a PR on nodejs/node to the `v18.x-staging` branch
gh workflow run create-node-pr.yml -f spec=next-9 -f branch=18

@github-actions github-actions bot force-pushed the release-please--branches--latest branch 4 times, most recently from f10ba56 to c732ed9 Compare December 17, 2022 03:38
@github-actions github-actions bot force-pushed the release-please--branches--latest branch 4 times, most recently from a73fd9e to c4aa0ca Compare January 2, 2023 00:26
@github-actions github-actions bot changed the title chore: release 9.2.1 chore: release 9.3.0 Jan 2, 2023
@github-actions github-actions bot force-pushed the release-please--branches--latest branch 2 times, most recently from b05cafa to e9711a0 Compare January 2, 2023 00:52
@ljharb
Copy link
Contributor

ljharb commented Jan 2, 2023

I'm confused; this release is already out, should this be merged?

@lukekarrys
Copy link
Contributor

the latest npm should be 9.2.0. @ljharb are you seeing something different?

@ljharb
Copy link
Contributor

ljharb commented Jan 2, 2023

oh oops, lol, i was thinking of node 19.3.0. ignore me

@lukekarrys lukekarrys mentioned this pull request Jan 2, 2023
Closed
@github-actions github-actions bot force-pushed the release-please--branches--latest branch 12 times, most recently from e6b58fb to 07e86f6 Compare January 12, 2023 18:07
@github-actions github-actions bot force-pushed the release-please--branches--latest branch from 07e86f6 to 868aeb5 Compare January 12, 2023 18:08
@lukekarrys lukekarrys merged commit 4d27592 into latest Jan 12, 2023
@lukekarrys lukekarrys deleted the release-please--branches--latest branch January 12, 2023 20:33
@github-actions
Copy link
Contributor Author

🤖 Release is at https://github.com/npm/cli/releases/tag/v9.3.0 🌻

@github-actions
Copy link
Contributor Author

🤖 Release is at https://github.com/npm/cli/releases/tag/arborist-v6.1.6 🌻

@github-actions
Copy link
Contributor Author

🤖 Release is at https://github.com/npm/cli/releases/tag/libnpmdiff-v5.0.7 🌻

@github-actions
Copy link
Contributor Author

🤖 Release is at https://github.com/npm/cli/releases/tag/libnpmexec-v5.0.7 🌻

@github-actions
Copy link
Contributor Author

🤖 Release is at https://github.com/npm/cli/releases/tag/libnpmfund-v4.0.7 🌻

@github-actions
Copy link
Contributor Author

🤖 Release is at https://github.com/npm/cli/releases/tag/libnpmpack-v5.0.7 🌻

@github-actions
Copy link
Contributor Author

🤖 Release is at https://github.com/npm/cli/releases/tag/config-v6.1.1 🌻

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
autorelease: tagged
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@ljharb @lukekarrys