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.1 #5752

Merged
merged 1 commit into from
Oct 26, 2022
Merged

chore: release 9.0.1 #5752

merged 1 commit into from
Oct 26, 2022

Conversation

github-actions[bot]
Copy link
Contributor

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

🤖 I have created a release beep boop

9.0.1

9.0.1 (2022-10-26)

Documentation

Dependencies

arborist: 6.1.0

6.1.0 (2022-10-26)

Features

Dependencies

libnpmdiff: 5.0.1

5.0.1 (2022-10-26)

Dependencies

libnpmexec: 5.0.1

5.0.1 (2022-10-26)

Dependencies

libnpmfund: 4.0.1

4.0.1 (2022-10-26)

Dependencies

libnpmpack: 5.0.1

5.0.1 (2022-10-26)

Dependencies

libnpmpublish: 7.0.1

7.0.1 (2022-10-26)

Dependencies


This PR was generated with Release Please. See documentation.

@github-actions
Copy link
Contributor Author

github-actions bot commented Oct 26, 2022

Release Manager

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

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.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 5752 --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
    node . publish -w libnpmdiff
    node . publish -w libnpmexec
    node . publish -w libnpmfund
    node . publish -w libnpmpack
    node . publish -w libnpmpublish
  • 5. Publish the CLI

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

    make publish
  • 6. Set dist-tag to published version

    Warning:
    NOT FOR PRERELEASE: Do not run this step for prereleases

    Note:
    You can optionally install via the version to see how it runs locally before tagging.

    Optionally install via version:

    Set version to latest dist tag:

    node . dist-tag add [email protected] latest
  • 7. Merge release PR

    gh pr merge --rebase
    git checkout latest
    git reset --hard origin/latest
    node . run resetdeps
  • 8. 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"`
    
  • 9. Post on Twitter

    New @npmjs release: 9.0.1!
    
    https://github.com/npm/cli/releases/tag/v9.0.1
    
    Release details...
    
  • 10. 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
  • 11. Open nodejs/node PR to update npm to latest

    Warning:
    NOT FOR PRERELEASE: Do not run this step for prereleases

    Sync our npm/node fork with the nodejs/node upstream:

    gh repo sync npm/node --source nodejs/node --force

    Trigger the Create CLI Deps PR action:

    gh workflow run create-cli-deps-pr.yml

@github-actions github-actions bot force-pushed the release-please--branches--latest branch 8 times, most recently from 33254b4 to f9f7344 Compare October 26, 2022 20:18
@github-actions github-actions bot force-pushed the release-please--branches--latest branch from f9f7344 to 903a31c Compare October 26, 2022 20:19
@nlf nlf merged commit ca93f3e into latest Oct 26, 2022
@nlf nlf deleted the release-please--branches--latest branch October 26, 2022 21:52
@github-actions
Copy link
Contributor Author

🤖 Release is at https://github.com/npm/cli/releases/tag/v9.0.1 🌻

@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