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.6 #5705

Merged
merged 1 commit into from
Oct 19, 2022
Merged

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Oct 17, 2022

🤖 I have created a release beep boop

9.0.0-pre.6

9.0.0-pre.6 (2022-10-19)

⚠️ BREAKING CHANGES

  • npm now outputs some json errors on stdout. Previously npm would output all json formatted errors on stderr, making it difficult to parse as the stderr stream usually has logs already written to it. In the future, npm will differentiate between errors and crashes. Errors, such as E404 and ERESOLVE, will be handled and will continue to be output on stdout. In the case of a crash, npm will log the error as usual but will not attempt to display it as json, even in --json mode. Moving a case from the category of an error to a crash will not be considered a breaking change. For more information see npm/rfcs#482.
  • npm config set will no longer accept deprecated or invalid config options.
  • timing and loglevel changes
    • timing has been removed as a value for --loglevel
    • --timing will show timing information regardless of
      --loglevel, except when --silent
  • deprecate boolean install flags in favor of --install-strategy
    • deprecate --global-style, --global now sets --install-strategy=shallow
    • deprecate --legacy-bundling, now sets --install-strategy=nested
  • npm will no longer attempt to modify ownership of files it creates
  • this package no longer attempts to change file ownership automatically
  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Documentation

Dependencies

arborist: 6.0.0-pre.5

6.0.0-pre.5 (2022-10-19)

⚠️ BREAKING CHANGES

  • deprecate boolean install flags in favor of --install-strategy
    • deprecate --global-style, --global now sets --install-strategy=shallow
    • deprecate --legacy-bundling, now sets --install-strategy=nested
  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Dependencies

libnpmaccess: 7.0.0-pre.2

7.0.0-pre.2 (2022-10-19)

Dependencies

  • 2008ea6 npm-package-arg@10.0.0, pacote@15.0.2
  • aa01072 #5707 update the following dependencies
libnpmdiff: 5.0.0-pre.3

5.0.0-pre.3 (2022-10-19)

Dependencies

libnpmexec: 5.0.0-pre.5

5.0.0-pre.5 (2022-10-19)

⚠️ BREAKING CHANGES

  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Dependencies

libnpmfund: 4.0.0-pre.5

4.0.0-pre.5 (2022-10-19)

Dependencies

libnpmhook: 9.0.0-pre.1

9.0.0-pre.1 (2022-10-19)

Dependencies

libnpmorg: 5.0.0-pre.1

5.0.0-pre.1 (2022-10-19)

Dependencies

libnpmpack: 5.0.0-pre.4

5.0.0-pre.4 (2022-10-19)

Dependencies

libnpmpublish: 7.0.0-pre.4

7.0.0-pre.4 (2022-10-19)

Dependencies

libnpmsearch: 6.0.0-pre.1

6.0.0-pre.1 (2022-10-19)

Dependencies

libnpmteam: 5.0.0-pre.1

5.0.0-pre.1 (2022-10-19)

Dependencies

libnpmversion: 4.0.0-pre.1

4.0.0-pre.1 (2022-10-19)

Dependencies


This PR was generated with Release Please. See documentation.

@github-actions
Copy link
Contributor Author

github-actions bot commented Oct 17, 2022

Release Manager

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

Force CI to Rerun for This Release

This PR will be updated and CI will run for every non-chore: commit that is pushed to main. To force CI to rerun, run this command:

gh workflow run release.yml -r latest

Release Checklist for v9.0.0-pre.6

  • 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 5705 --force
    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 libnpmaccess --tag prerelease
    node . publish -w libnpmdiff --tag prerelease
    node . publish -w libnpmexec --tag prerelease
    node . publish -w libnpmfund --tag prerelease
    node . publish -w libnpmhook --tag prerelease
    node . publish -w libnpmorg --tag prerelease
    node . publish -w libnpmpack --tag prerelease
    node . publish -w libnpmpublish --tag prerelease
    node . publish -w libnpmsearch --tag prerelease
    node . publish -w libnpmteam --tag prerelease
    node . publish -w libnpmversion --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 reset --hard origin/latest
    node . run resetdeps
  • 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.6!
    
    https://github.com/npm/cli/releases/tag/v9.0.0-pre.6
    
    Release details...
    
  • 9. Trigger docs.npmjs.com update

    Warning:
    The releases.json will need to be updated when a new major release is tagged latest.

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

@github-actions github-actions bot force-pushed the release-please--branches--latest branch 4 times, most recently from bb55670 to 0bbc501 Compare October 18, 2022 07:13
@github-actions github-actions bot force-pushed the release-please--branches--latest branch 22 times, most recently from a2daa13 to ec5c9a6 Compare October 19, 2022 19:12
@github-actions github-actions bot force-pushed the release-please--branches--latest branch from e72d18d to 728b24b Compare October 19, 2022 19:57
@lukekarrys lukekarrys merged commit 2929899 into latest Oct 19, 2022
@lukekarrys lukekarrys deleted the release-please--branches--latest branch October 19, 2022 20:48
@github-actions
Copy link
Contributor Author

@github-actions
Copy link
Contributor Author

@github-actions
Copy link
Contributor Author

@github-actions
Copy link
Contributor Author

@github-actions
Copy link
Contributor Author

@github-actions
Copy link
Contributor Author

@github-actions
Copy link
Contributor Author

@github-actions
Copy link
Contributor Author

@github-actions
Copy link
Contributor Author

@github-actions
Copy link
Contributor Author

@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