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

chore: release 9.1.1 #5821

Merged
merged 1 commit into from
Nov 9, 2022
Merged

chore: release 9.1.1 #5821

merged 1 commit into from
Nov 9, 2022

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Nov 7, 2022

🤖 I have created a release beep boop

9.1.1

9.1.1 (2022-11-09)

Documentation

Dependencies

arborist: 6.1.2

6.1.2 (2022-11-09)

Dependencies

libnpmdiff: 5.0.3

5.0.3 (2022-11-09)

Dependencies

libnpmexec: 5.0.3

5.0.3 (2022-11-09)

Bug Fixes

Dependencies

libnpmfund: 4.0.3

4.0.3 (2022-11-09)

Dependencies

libnpmpack: 5.0.3

5.0.3 (2022-11-09)

Dependencies

libnpmpublish: 7.0.3

7.0.3 (2022-11-09)

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 November 7, 2022 23:39
@github-actions
Copy link
Contributor Author

github-actions bot commented Nov 7, 2022

Release Manager

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

Force CI to Rerun for This Release

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

gh workflow run release.yml -r latest

Release Checklist for v9.1.1

  • 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 5821 --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.1.1!
    
    https://github.com/npm/cli/releases/tag/v9.1.1
    
    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

    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 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 9 times, most recently from 60cfd17 to 822a585 Compare November 9, 2022 21:01
@lukekarrys lukekarrys force-pushed the release-please--branches--latest branch from 822a585 to 8c5c1c6 Compare November 9, 2022 21:03
@github-actions github-actions bot force-pushed the release-please--branches--latest branch from 8c5c1c6 to 26dbff8 Compare November 9, 2022 21:18
@github-actions github-actions bot force-pushed the release-please--branches--latest branch from 26dbff8 to 243a84a Compare November 9, 2022 21:19
@lukekarrys lukekarrys merged commit 3794f03 into latest Nov 9, 2022
@lukekarrys lukekarrys deleted the release-please--branches--latest branch November 9, 2022 21:39
@github-actions
Copy link
Contributor Author

github-actions bot commented Nov 9, 2022

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

@github-actions
Copy link
Contributor Author

github-actions bot commented Nov 9, 2022

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

@github-actions
Copy link
Contributor Author

github-actions bot commented Nov 9, 2022

@github-actions
Copy link
Contributor Author

github-actions bot commented Nov 9, 2022

@github-actions
Copy link
Contributor Author

github-actions bot commented Nov 9, 2022

@github-actions
Copy link
Contributor Author

github-actions bot commented Nov 9, 2022

@github-actions
Copy link
Contributor Author

github-actions bot commented Nov 9, 2022

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.

1 participant