Skip to content

chore: release 10.2.0 #6790

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
Oct 3, 2023
Merged

chore: release 10.2.0 #6790

merged 1 commit into from
Oct 3, 2023

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Sep 11, 2023 •
edited
Loading

🤖 I have created a release beep boop

10.2.0

10.2.0 (2023-10-02)

Features

Bug Fixes

Documentation

Dependencies

arborist: 7.2.0

7.2.0 (2023-10-02)

Features

Bug Fixes

Dependencies

config: 8.0.0

8.0.0 (2023-10-02)

⚠️ BREAKING CHANGES

  • @npmcli/config now supports node ^16.14.0 || >=18.0.0

Features

Bug Fixes

Documentation

libnpmaccess: 8.0.1

8.0.1 (2023-10-02)

Dependencies

libnpmdiff: 6.0.2

6.0.2 (2023-10-02)

Dependencies

libnpmexec: 7.0.2

7.0.2 (2023-10-02)

Dependencies

libnpmfund: 5.0.0

5.0.0 (2023-10-02)

⚠️ BREAKING CHANGES

  • libnpmfund now supports node ^16.14.0 || >=18.0.0

Bug Fixes

Dependencies

libnpmorg: 6.0.1

6.0.1 (2023-10-02)

Dependencies

libnpmpack: 6.0.2

6.0.2 (2023-10-02)

Dependencies

libnpmpublish: 9.0.1

9.0.1 (2023-10-02)

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 September 11, 2023 17:38
@github-actions
Copy link
Contributor Author

github-actions bot commented Sep 11, 2023 •
edited
Loading

Release Manager

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

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=6790

Release Checklist for v10.2.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 6790 --force
    npm run resetdeps
    node scripts/git-dirty.js

  • 2. Check CI status

    gh pr checks --watch

  • 3. Publish the CLI and workspaces

    Warning:
    This will publish all updated workspaces to latest, prerelease or backport depending on their version, and will publish the CLI with the dist-tag set to next-10.

    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 10 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. These are done once this PR has been labelled with autorelease: tagged.

    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. Mark GitHub Release as latest

    Warning:
    You must wait for CI to create the release tags before running this step. These are done once this PR has been labelled with autorelease: tagged.

    Release Please will make GitHub Releases for the CLI and all workspaces, but GitHub has UI affordances for which release should appear as the "latest", which should always be the CLI. To mark the CLI release as latest run this command:

    gh release -R npm/cli edit v10.2.0 --latest

  • 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. These are done once this PR has been labelled with autorelease: tagged.

    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.

    First, sync our fork of node with the upstream source:

    gh repo sync npm/node --source nodejs/node --force

    Then, if we are opening a PR against the latest version of node:

    gh workflow run create-node-pr.yml -f spec=next-10

    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).

    For example, this will create a PR on nodejs/node to the v16.x-staging branch:

    gh workflow run create-node-pr.yml -f spec=next-10 -f branch=16

  • 11. 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 from c1af014 to e06d6be Compare September 11, 2023 17:40
@github-actions github-actions bot changed the title chore: release 10.1.1 chore: release 10.2.0 Sep 11, 2023
@github-actions github-actions bot force-pushed the release-please--branches--latest branch 10 times, most recently from 982940e to d99d34b Compare September 18, 2023 18:19
@github-actions github-actions bot force-pushed the release-please--branches--latest branch 8 times, most recently from b869d81 to f871064 Compare September 26, 2023 19:25
@github-actions github-actions bot force-pushed the release-please--branches--latest branch 7 times, most recently from 6a812fe to ee80a2f Compare October 2, 2023 21:58
@github-actions github-actions bot force-pushed the release-please--branches--latest branch 2 times, most recently from 226a1d3 to f211519 Compare October 2, 2023 22:37
@github-actions github-actions bot force-pushed the release-please--branches--latest branch from f211519 to 26415f4 Compare October 2, 2023 22:38
@lukekarrys lukekarrys merged commit 57a8957 into latest Oct 3, 2023
@lukekarrys lukekarrys deleted the release-please--branches--latest branch October 3, 2023 15:59
@github-actions
Copy link
Contributor Author

github-actions bot commented Oct 3, 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. 🚨

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.

1 participant

@lukekarrys