cli icon indicating copy to clipboard operation
cli copied to clipboard
verified publisher icon npm

chore: release 11.0.0-pre

Open github-actions[bot] opened this issue 1 year ago • 1 comments

:robot: I have created a release beep boop

11.0.0-pre

11.0.0-pre (2024-10-18)

⚠️ BREAKING CHANGES

  • npm will no longer switch to global mode if aliased to "npmg" or "npm-g" etc.
  • The npm hook command has been removed
  • Attestations made by this package will no longer validate in npm versions prior to 10.6.0
  • npm now supports node ^20.17.0 || >=22.9.0
  • @npmcli/docs now supports node ^20.17.0 || >=22.9.0

Bug Fixes

  • 780afc5 #7855 pkg: display if any of multiple attributes exist (#7855) (@Sanderovich)
  • ecd2d23 #7842 don't go into global mode if aliased to npmg (#7842) (@wraithgar)
  • 62c71e5 #7835 removes npm hook command (@reggi)
  • 7f541e8 #7815 make pack and exec work with git hash refs (#7815) (@milaninfy)
  • 3162620 #7831 sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)
  • 4c8ba0a #7831 for @npmcli/docs sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)
  • 70cd88d #7808 view: sort and truncate dist-tags (#7808) (@wraithgar)
  • 534ad77 #7795 remove unused parameters catch statements (#7795) (@btea)

Documentation

  • feb54f7 #7822 package.json: add libc field (#7822) (@wraithgar)

Dependencies

Chores

arborist: 9.0.0-pre

9.0.0-pre (2024-10-18)

⚠️ BREAKING CHANGES

  • @npmcli/arborist now supports node ^20.17.0 || >=22.9.0

Bug Fixes

  • 3ffc08b #7831 for @npmcli/arborist sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)
config: 10.0.0-pre

10.0.0-pre (2024-10-18)

⚠️ BREAKING CHANGES

  • @npmcli/config now supports node ^20.17.0 || >=22.9.0

Bug Fixes

  • 6e11eb2 #7831 for @npmcli/config sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)
libnpmaccess: 10.0.0-pre

10.0.0-pre (2024-10-18)

⚠️ BREAKING CHANGES

  • libnpmaccess now supports node ^20.17.0 || >=22.9.0

Bug Fixes

  • 687cfaf #7831 for libnpmaccess sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)
libnpmdiff: 8.0.0-pre

8.0.0-pre (2024-10-18)

⚠️ BREAKING CHANGES

  • libnpmdiff now supports node ^20.17.0 || >=22.9.0

Bug Fixes

  • dab3042 #7831 for libnpmdiff sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)

Dependencies

libnpmexec: 10.0.0-pre

10.0.0-pre (2024-10-18)

⚠️ BREAKING CHANGES

  • libnpmexec now supports node ^20.17.0 || >=22.9.0

Bug Fixes

  • 7f541e8 #7815 make pack and exec work with git hash refs (#7815) (@milaninfy)
  • 2902d4c #7831 for libnpmexec sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)

Dependencies

libnpmfund: 7.0.0-pre

7.0.0-pre (2024-10-18)

⚠️ BREAKING CHANGES

  • libnpmfund now supports node ^20.17.0 || >=22.9.0

Bug Fixes

  • 44be07c #7831 for libnpmfund sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)

Dependencies

libnpmorg: 8.0.0-pre

8.0.0-pre (2024-10-18)

⚠️ BREAKING CHANGES

  • libnpmorg now supports node ^20.17.0 || >=22.9.0

Bug Fixes

  • 62c4604 #7831 for libnpmorg sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)
libnpmpack: 9.0.0-pre

9.0.0-pre (2024-10-18)

⚠️ BREAKING CHANGES

  • libnpmpack now supports node ^20.17.0 || >=22.9.0

Bug Fixes

  • 7f541e8 #7815 make pack and exec work with git hash refs (#7815) (@milaninfy)
  • f7b41a3 #7831 for libnpmpack sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)

Dependencies

libnpmpublish: 11.0.0-pre

11.0.0-pre (2024-10-18)

⚠️ BREAKING CHANGES

  • Attestations made by this package will no longer validate in npm versions prior to 10.6.0
  • libnpmpublish now supports node ^20.17.0 || >=22.9.0

Bug Fixes

  • f75da94 #7833 update libnpmpublish tests for sigstore 3.0.0 (@bdehamer)
  • a2f8af0 #7831 for libnpmpublish sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)

Dependencies

libnpmsearch: 9.0.0-pre

9.0.0-pre (2024-10-18)

⚠️ BREAKING CHANGES

  • libnpmsearch now supports node ^20.17.0 || >=22.9.0

Bug Fixes

  • 2f2ee15 #7831 for libnpmsearch sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)
libnpmteam: 8.0.0-pre

8.0.0-pre (2024-10-18)

⚠️ BREAKING CHANGES

  • libnpmteam now supports node ^20.17.0 || >=22.9.0

Bug Fixes

  • 9561fa7 #7831 for libnpmteam sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)
libnpmversion: 8.0.0-pre

8.0.0-pre (2024-10-18)

⚠️ BREAKING CHANGES

  • libnpmversion now supports node ^20.17.0 || >=22.9.0

Bug Fixes

  • 57eef8d #7831 for libnpmversion sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)

This PR was generated with Release Please. See documentation.

github-actions[bot] avatar Oct 03 '24 18:10 github-actions[bot]

Release Manager

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

Release Checklist for v11.0.0-pre.0

  • [x] 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 7813 --force

    npm run resetdeps

    node scripts/git-dirty.js

  • [x] 2. Check CI status

    gh pr checks --watch

  • [x] 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-11.

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

    node scripts/publish.js --test

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

    npm i -g [email protected]

    npm --version
npm whoami
npm help install
# etc

  • [ ] 5. Trigger docs.npmjs.com update

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

  • [ ] 6. Approve and Merge release PR

    gh pr review --approve

    gh pr merge --rebase

    git checkout latest

    git fetch

    git reset --hard origin/latest

    node . run resetdeps

  • [ ] 7. 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"`

  • [ ] 8. 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 v11.0.0-pre.0 --latest

  • [ ] 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. 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-11

    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-11 -f branch=16

  • [ ] 10. 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[bot] avatar Oct 03 '24 18:10 github-actions[bot]

🤖 Created releases:

:sunflower:

github-actions[bot] avatar Nov 26 '24 19:11 github-actions[bot]

Release Workflow

:rotating_light::rotating_light::rotating_light:

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

:rotating_light::rotating_light::rotating_light:

github-actions[bot] avatar Nov 26 '24 19:11 github-actions[bot]