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.

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

chore: release 11.0.0-pre.1 #7953

Merged
merged 1 commit into from
Dec 6, 2024
Merged

chore: release 11.0.0-pre.1 #7953

merged 1 commit into from
Dec 6, 2024

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Dec 2, 2024 •
edited
Loading

🤖 I have created a release beep boop

11.0.0-pre.1

11.0.0-pre.1 (2024-12-06)

⚠️ BREAKING CHANGES

  • Upon publishing, in order to apply a default "latest" dist tag, the command now retrieves all prior versions of the package. It will require that the version you're trying to publish is above the latest semver version in the registry, not including pre-release tags.
  • npm init now has a type prompt, and sorts the entries the created packages differently
  • bun.lockb files are now included in the strict ignore list during packing

Features

Bug Fixes

Documentation

Dependencies

Chores

arborist: 9.0.0-pre.1

9.0.0-pre.1 (2024-12-06)

⚠️ BREAKING CHANGES

  • Upon publishing, in order to apply a default "latest" dist tag, the command now retrieves all prior versions of the package. It will require that the version you're trying to publish is above the latest semver version in the registry, not including pre-release tags.
  • bun.lockb files are now included in the strict ignore list during packing

Features

Dependencies

config: 10.0.0-pre.1

10.0.0-pre.1 (2024-12-06)

Documentation

Dependencies

libnpmdiff: 8.0.0-pre.1

8.0.0-pre.1 (2024-12-06)

⚠️ BREAKING CHANGES

  • bun.lockb files are now included in the strict ignore list during packing

Dependencies

libnpmexec: 10.0.0-pre.1

10.0.0-pre.1 (2024-12-06)

⚠️ BREAKING CHANGES

  • bun.lockb files are now included in the strict ignore list during packing

Dependencies

libnpmfund: 7.0.0-pre.1

Dependencies

libnpmorg: 8.0.0-pre.1

8.0.0-pre.1 (2024-12-06)

⚠️ BREAKING CHANGES

  • Upon publishing, in order to apply a default "latest" dist tag, the command now retrieves all prior versions of the package. It will require that the version you're trying to publish is above the latest semver version in the registry, not including pre-release tags.

Features

libnpmpack: 9.0.0-pre.1

9.0.0-pre.1 (2024-12-06)

⚠️ BREAKING CHANGES

  • bun.lockb files are now included in the strict ignore list during packing

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 December 2, 2024 16:21
@github-actions GitHub Actions
Copy link
Contributor Author

github-actions bot commented Dec 2, 2024 •
edited by wraithgar
Loading

Release Manager

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

Release Checklist for v11.0.0-pre.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 7953 --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-11.

    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 npm@11.0.0-pre.1 locally

    npm i -g npm@11.0.0-pre.1
    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.1 --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 github-actions bot force-pushed the release-please--branches--latest branch 8 times, most recently from 6c8ef33 to 2fb06f6 Compare December 6, 2024 16:41
@github-actions github-actions bot force-pushed the release-please--branches--latest branch from 2fb06f6 to e5811d3 Compare December 6, 2024 16:41
@wraithgar wraithgar merged commit cf52b8b into latest Dec 6, 2024
18 checks passed
@wraithgar wraithgar deleted the release-please--branches--latest branch December 6, 2024 17:14
@github-actions GitHub Actions
Copy link
Contributor Author

github-actions bot commented Dec 6, 2024

🤖 Created releases:

🌻

@github-actions GitHub Actions
Copy link
Contributor Author

github-actions bot commented Dec 6, 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

@wraithgar wraithgar wraithgar approved these changes

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