Skip to content

chore: release 10.9.0#7777

Merged
wraithgar merged 1 commit into
latestfrom
release-please--branches--latest
Oct 3, 2024
Merged

chore: release 10.9.0#7777
wraithgar merged 1 commit into
latestfrom
release-please--branches--latest

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented Sep 11, 2024 •
edited
Loading

🤖 I have created a release beep boop

10.9.0

10.9.0 (2024-10-03)

Features

Bug Fixes

Documentation

Dependencies

Chores

arborist: 8.0.0

8.0.0 (2024-10-03)

⚠️ BREAKING CHANGES

  • @npmcli/arborist now supports node ^18.17.0 || >=20.5.0

Features

Bug Fixes

Dependencies

Chores

config: 9.0.0

9.0.0 (2024-10-03)

⚠️ BREAKING CHANGES

  • @npmcli/config now supports node ^18.17.0 || >=20.5.0

Bug Fixes

Dependencies

Chores

libnpmaccess: 9.0.0

9.0.0 (2024-10-03)

⚠️ BREAKING CHANGES

  • libnpmaccess now supports node ^18.17.0 || >=20.5.0

Bug Fixes

Dependencies

Chores

libnpmdiff: 7.0.0

7.0.0 (2024-10-03)

⚠️ BREAKING CHANGES

  • libnpmdiff now supports node ^18.17.0 || >=20.5.0

Bug Fixes

Dependencies

Chores

libnpmexec: 9.0.0

9.0.0 (2024-10-03)

⚠️ BREAKING CHANGES

  • libnpmexec now supports node ^18.17.0 || >=20.5.0

Bug Fixes

Dependencies

Chores

libnpmfund: 6.0.0

6.0.0 (2024-10-03)

⚠️ BREAKING CHANGES

  • libnpmfund now supports node ^18.17.0 || >=20.5.0

Bug Fixes

Chores

Dependencies

libnpmhook: 11.0.0

11.0.0 (2024-10-03)

⚠️ BREAKING CHANGES

  • libnpmhook now supports node ^18.17.0 || >=20.5.0

Bug Fixes

Dependencies

Chores

libnpmorg: 7.0.0

7.0.0 (2024-10-03)

⚠️ BREAKING CHANGES

  • libnpmorg now supports node ^18.17.0 || >=20.5.0

Bug Fixes

Dependencies

Chores

libnpmpack: 8.0.0

8.0.0 (2024-10-03)

⚠️ BREAKING CHANGES

  • libnpmpack now supports node ^18.17.0 || >=20.5.0

Bug Fixes

Dependencies

Chores

libnpmpublish: 10.0.0

10.0.0 (2024-10-03)

⚠️ BREAKING CHANGES

  • libnpmpublish now supports node ^18.17.0 || >=20.5.0

Bug Fixes

Dependencies

Chores

libnpmsearch: 8.0.0

8.0.0 (2024-10-03)

⚠️ BREAKING CHANGES

  • libnpmsearch now supports node ^18.17.0 || >=20.5.0

Bug Fixes

Dependencies

Chores

libnpmteam: 7.0.0

7.0.0 (2024-10-03)

⚠️ BREAKING CHANGES

  • libnpmteam now supports node ^18.17.0 || >=20.5.0

Bug Fixes

Dependencies

Chores

libnpmversion: 7.0.0

7.0.0 (2024-10-03)

⚠️ BREAKING CHANGES

  • libnpmversion now supports node ^18.17.0 || >=20.5.0

Bug Fixes

Dependencies

Chores

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, 2024 15:47
@github-actions
Copy link
Copy Markdown
Contributor Author

github-actions Bot commented Sep 11, 2024 •
edited
Loading

Release Manager

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

Release Checklist for v10.9.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 7777 --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.9.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. This could be you!

    • 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 3 times, most recently from 68cdbb3 to f007cec Compare September 17, 2024 19:46
@github-actions github-actions Bot changed the title chore: release 10.8.4 chore: release 11.0.0 Sep 26, 2024
@github-actions github-actions Bot force-pushed the release-please--branches--latest branch 4 times, most recently from 367cace to 2f6fb25 Compare September 26, 2024 19:46
@github-actions github-actions Bot changed the title chore: release 11.0.0 chore: release 10.8.4 Sep 26, 2024
@github-actions github-actions Bot force-pushed the release-please--branches--latest branch 4 times, most recently from 5abfa6b to af6b70b Compare September 30, 2024 14:22
@github-actions github-actions Bot changed the title chore: release 10.8.4 chore: release 11.0.0 Oct 2, 2024
@github-actions github-actions Bot force-pushed the release-please--branches--latest branch 2 times, most recently from 39563e1 to 5d50690 Compare October 2, 2024 18:29
@github-actions github-actions Bot changed the title chore: release 11.0.0 chore: release 10.8.4 Oct 2, 2024
@github-actions github-actions Bot force-pushed the release-please--branches--latest branch 2 times, most recently from 4fba788 to 6096785 Compare October 2, 2024 18:59
@github-actions github-actions Bot changed the title chore: release 10.8.4 chore: release 10.9.0 Oct 3, 2024
@github-actions github-actions Bot force-pushed the release-please--branches--latest branch from 6096785 to 3873e7b Compare October 3, 2024 16:46
@github-actions github-actions Bot force-pushed the release-please--branches--latest branch from 3873e7b to 9afb2f8 Compare October 3, 2024 16:47
@wraithgar wraithgar merged commit 977fd57 into latest Oct 3, 2024
@wraithgar wraithgar deleted the release-please--branches--latest branch October 3, 2024 17:56
@github-actions
Copy link
Copy Markdown
Contributor Author

github-actions Bot commented Oct 3, 2024

🤖 Created releases:

@github-actions
Copy link
Copy Markdown
Contributor Author

github-actions Bot commented Oct 3, 2024 •
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.

🚨🚨🚨

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

Reviewers

1 more reviewer

@wraithgar wraithgar wraithgar approved these changes

Reviewers whose approvals may not affect merge requirements

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

@wraithgar