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 10.0.0-pre.1 #6682

Merged
merged 1 commit into from
Aug 31, 2023
Merged

chore: release 10.0.0-pre.1 #6682

merged 1 commit into from
Aug 31, 2023

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jul 28, 2023 •
edited
Loading

🤖 I have created a release beep boop

10.0.0-pre.1

10.0.0-pre.1 (2023-08-31)

⚠️ BREAKING CHANGES

  • support for node <=16.13 has been removed
  • support for node 14 has been removed
  • support for node 14 has been removed
  • support for node 14 has been removed
  • support for node 14 has been removed
  • support for node 14 has been removed
  • support for node 14 has been removed
  • support for node 14 has been removed
  • support for node 14 has been removed
  • support for node 14 has been removed
  • support for node 14 has been removed

Bug Fixes

Documentation

Dependencies

arborist: 7.0.0-pre.0

7.0.0-pre.0 (2023-08-31)

⚠️ BREAKING CHANGES

  • support for node <=16.13 has been removed
  • support for node 14 has been removed

Bug Fixes

Dependencies

config: 7.0.1

7.0.1 (2023-08-31)

Bug Fixes

libnpmaccess: 8.0.0-pre.0

8.0.0-pre.0 (2023-08-31)

⚠️ BREAKING CHANGES

  • support for node <=16.13 has been removed
  • support for node 14 has been removed

Bug Fixes

Dependencies

libnpmdiff: 6.0.0-pre.0

6.0.0-pre.0 (2023-08-31)

⚠️ BREAKING CHANGES

  • support for node <=16.13 has been removed
  • support for node 14 has been removed

Bug Fixes

Dependencies

libnpmexec: 7.0.0-pre.0

7.0.0-pre.0 (2023-08-31)

⚠️ BREAKING CHANGES

  • support for node <=16.13 has been removed
  • support for node 14 has been removed

Bug Fixes

Dependencies

libnpmfund: 4.0.20

4.0.20 (2023-08-31)

Dependencies

libnpmhook: 10.0.0-pre.0

10.0.0-pre.0 (2023-08-31)

⚠️ BREAKING CHANGES

  • support for node <=16.13 has been removed
  • support for node 14 has been removed

Bug Fixes

Dependencies

libnpmorg: 6.0.0-pre.0

6.0.0-pre.0 (2023-08-31)

⚠️ BREAKING CHANGES

  • support for node <=16.13 has been removed
  • support for node 14 has been removed

Bug Fixes

Dependencies

libnpmpack: 6.0.0-pre.0

6.0.0-pre.0 (2023-08-31)

⚠️ BREAKING CHANGES

  • support for node <=16.13 has been removed
  • support for node 14 has been removed

Bug Fixes

Dependencies

libnpmpublish: 9.0.0-pre.0

9.0.0-pre.0 (2023-08-31)

⚠️ BREAKING CHANGES

  • support for node <=16.13 has been removed
  • support for node 14 has been removed

Bug Fixes

Dependencies

libnpmsearch: 7.0.0-pre.0

7.0.0-pre.0 (2023-08-31)

⚠️ BREAKING CHANGES

  • support for node <=16.13 has been removed
  • support for node 14 has been removed

Bug Fixes

Dependencies

libnpmteam: 6.0.0-pre.0

6.0.0-pre.0 (2023-08-31)

⚠️ BREAKING CHANGES

  • support for node <=16.13 has been removed
  • support for node 14 has been removed

Bug Fixes

Dependencies

libnpmversion: 5.0.0-pre.0

5.0.0-pre.0 (2023-08-31)

⚠️ BREAKING CHANGES

  • support for node <=16.13 has been removed

Bug Fixes

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 July 28, 2023 13:55
@github-actions
Copy link
Contributor Author

github-actions bot commented Jul 28, 2023 •
edited by lukekarrys
Loading

Release Manager

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

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

Release Checklist for v10.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 6682 --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. Trigger docs.npmjs.com update

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

  • 6. Merge release PR

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

  • 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 5 times, most recently from 4e86772 to c0ed42b Compare July 31, 2023 21:21
@github-actions github-actions bot force-pushed the release-please--branches--latest branch 4 times, most recently from 6a8901c to dd6e927 Compare August 18, 2023 05:48
@github-actions github-actions bot force-pushed the release-please--branches--latest branch 5 times, most recently from 73c92a1 to dee0670 Compare August 31, 2023 18:33
@github-actions github-actions bot force-pushed the release-please--branches--latest branch from dee0670 to 4f18871 Compare August 31, 2023 18:34
@lukekarrys lukekarrys merged commit 52cb638 into latest Aug 31, 2023
14 of 22 checks passed
@lukekarrys lukekarrys deleted the release-please--branches--latest branch August 31, 2023 19:02
@github-actions
Copy link
Contributor Author

github-actions bot commented Aug 31, 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