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.

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

chore: release 9.0.0-pre.2 #5552

Merged
merged 1 commit into from
Sep 23, 2022
Merged

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Sep 21, 2022

🤖 I have created a release beep boop

9.0.0-pre.2

9.0.0-pre.2 (2022-09-23)

⚠️ BREAKING CHANGES

  • the default auth-type config value is now web
  • login, adduser, and auth-type changes
    • This removes all auth-type configs except web and legacy.
    • login and adduser are now separate commands that send different data to the registry.
    • auth-type config values web and legacy only try
      their respective methods, npm no longer tries them all and waits to see
      which one doesn't fail.

Features

Bug Fixes

Documentation

Dependencies

arborist: 6.0.0-pre.2

6.0.0-pre.2 (2022-09-23)

Features

Documentation

Dependencies

libnpmexec: 5.0.0-pre.2

5.0.0-pre.2 (2022-09-23)

Dependencies

libnpmfund: 4.0.0-pre.2

4.0.0-pre.2 (2022-09-23)

Dependencies


This PR was generated with Release Please. See documentation.

@github-actions
Copy link
Contributor Author

github-actions bot commented Sep 21, 2022

Release Manager

Release Checklist for v9.0.0-pre.2

  • 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 5552
    node . run resetdeps
    node scripts/git-dirty.js
  • 2. Run tests locally

    These have also been running in CI continuously each time the release PR was updated, but it is nice to confirm they pass locally since that is where we will be publishing from.

    node . run lint-all
    node . run test-all
    node scripts/git-dirty.js
  • 3. Check CI status

    gh pr checks --watch
  • 4. Publish workspaces

    Note:
    If we are currently publishing prereleases, make sure to publish with the prerelease tag.

    node . publish -w @npmcli/arborist --tag prerelease
    node . publish -w libnpmexec --tag prerelease
    node . publish -w libnpmfund --tag prerelease
  • 5. Publish the CLI

    Note:
    This will publish with the dist-tag set to next-9

    make publish
  • 6. Merge release PR

    gh pr merge --rebase
    git checkout latest
    git pull
  • 7. Check For Release Tags

    Release Please will run on the just pushed release commit and create GitHub releases and tags for each package.

    gh run watch `gh run list -w release -L 1 --json databaseId -q ".[0].databaseId"`
    
  • 8. Post on Twitter

    New @npmjs release: 9.0.0-pre.2!
    
    https://github.com/npm/cli/releases/tag/v9.0.0-pre.2
    
    Release details...
    

@github-actions github-actions bot force-pushed the release-please--branches--latest branch 17 times, most recently from 1f1406d to daa1d1d Compare September 23, 2022 03:50
@github-actions github-actions bot force-pushed the release-please--branches--latest branch from daa1d1d to 7e1a870 Compare September 23, 2022 03:51
@lukekarrys lukekarrys merged commit 84598fe into latest Sep 23, 2022
@lukekarrys lukekarrys deleted the release-please--branches--latest branch September 23, 2022 06:00
@github-actions
Copy link
Contributor Author

🤖 Release is at https://github.com/npm/cli/releases/tag/v9.0.0-pre.2 🌻

@github-actions
Copy link
Contributor Author

@github-actions
Copy link
Contributor Author

@github-actions
Copy link
Contributor Author

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

Successfully merging this pull request may close these issues.

1 participant