Skip to content

chore: release 9.4.2 #6140

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
Merged
merged 1 commit into from
Feb 7, 2023
Merged

chore: release 9.4.2 #6140

merged 1 commit into from
Feb 7, 2023

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Feb 7, 2023 •
edited
Loading

🤖 I have created a release beep boop

9.4.2

9.4.2 (2023-02-07)

Bug Fixes

Documentation

Dependencies

arborist: 6.2.2

6.2.2 (2023-02-07)

Bug Fixes

Dependencies

config: 6.1.3

6.1.3 (2023-02-07)

Dependencies

libnpmdiff: 5.0.10

5.0.10 (2023-02-07)

Bug Fixes

Dependencies

libnpmexec: 5.0.10

5.0.10 (2023-02-07)

Dependencies

libnpmfund: 4.0.10

4.0.10 (2023-02-07)

Bug Fixes

Dependencies

libnpmhook: 9.0.3

9.0.3 (2023-02-07)

Bug Fixes

libnpmorg: 5.0.3

5.0.3 (2023-02-07)

Dependencies

libnpmpack: 5.0.10

5.0.10 (2023-02-07)

Dependencies

libnpmpublish: 7.0.8

7.0.8 (2023-02-07)

Bug Fixes

This PR was generated with Release Please. See documentation.

@github-actions github-actions bot requested a review from a team as a code owner February 7, 2023 04:52
@github-actions github-actions bot requested review from fritzy and removed request for a team February 7, 2023 04:52
@github-actions
Copy link
Contributor Author

github-actions bot commented Feb 7, 2023 •
edited by lukekarrys
Loading

Release Manager

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

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 -R npm/cli -f release-pr=6140

Release Checklist for v9.4.2

  • 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 6140 --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. Trigger docs.npmjs.com update

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

  • 7. Merge release PR

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

  • 8. Wait For Release Tags

    Warning:
    The remaining steps all require the GitHub tags and releases to be created first.

    Release Please will run on the just merged release commit and create GitHub releases and tags for each package. The release bot will will comment on this PR when the releases and tags are created.

    Note:
    The release workflow also includes the Node integration tests which do not need to finish before continuing.

    You can watch the release workflow in your terminal with the following command:

    gh run watch `gh run list -R npm/cli -w release -b latest -L 1 --json databaseId -q ".[0].databaseId"`

  • 9. 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

  • 10. Label and fast-track nodejs/node PR

    Note:
    This requires being a nodejs collaborator. Currently @lukekarrys is so ping them to do these steps!

    • Thumbs-up reaction on the Fast-track comment
    • Add an LGTM / Approval
    • Add request-ci label to get it running CI
    • Add commit-queue label once everything is green

@github-actions github-actions bot force-pushed the release-please--branches--latest branch 6 times, most recently from d8b9ff8 to 67a6c80 Compare February 7, 2023 20:32
@github-actions github-actions bot force-pushed the release-please--branches--latest branch from 67a6c80 to f11c6fc Compare February 7, 2023 20:33
@lukekarrys lukekarrys merged commit e7284b6 into latest Feb 7, 2023
@lukekarrys lukekarrys deleted the release-please--branches--latest branch February 7, 2023 20:54
@npm npm deleted a comment from github-actions bot Feb 7, 2023
@github-actions
Copy link
Contributor Author

github-actions bot commented Feb 7, 2023 •
edited
Loading

Release Workflow

@github-actions
Copy link
Contributor Author

github-actions bot commented Feb 8, 2023 •
edited
Loading

Release Workflow

🚨 @npm/cli-team: The post-release workflow failed for this release. Manual steps may need to be taken after examining the workflow output from the above workflow run. 🚨

@github-actions
Copy link
Contributor Author

github-actions bot commented Feb 8, 2023 •
edited
Loading

Release Workflow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@fritzy fritzy Awaiting requested review from fritzy fritzy is a code owner automatically assigned from npm/cli-team

Assignees

No one assigned

Labels

autorelease: tagged

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@lukekarrys