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.4 #5632

Merged
merged 1 commit into from
Oct 5, 2022
Merged

Conversation

github-actions[bot]
Copy link
Contributor

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

🤖 I have created a release beep boop

9.0.0-pre.4

9.0.0-pre.4 (2022-10-05)

Features

Bug Fixes

Documentation

Dependencies

arborist: 6.0.0-pre.4

6.0.0-pre.4 (2022-10-05)

Features

Dependencies

libnpmdiff: 5.0.0-pre.2

5.0.0-pre.2 (2022-10-05)

Dependencies

libnpmexec: 5.0.0-pre.4

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

Dependencies

libnpmfund: 4.0.0-pre.4

4.0.0-pre.4 (2022-10-05)

Dependencies

libnpmpack: 5.0.0-pre.2

5.0.0-pre.2 (2022-10-05)

Bug Fixes

Dependencies

libnpmpublish: 7.0.0-pre.2

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

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 October 3, 2022 18:33
@github-actions
Copy link
Contributor Author

github-actions bot commented Oct 3, 2022

Release Manager

Release Checklist for v9.0.0-pre.4

  • 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 5632 --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 libnpmdiff --tag prerelease
    node . publish -w libnpmexec --tag prerelease
    node . publish -w libnpmfund --tag prerelease
    node . publish -w libnpmpack --tag prerelease
    node . publish -w libnpmpublish --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 resetdepts
  • 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.4!
    
    https://github.com/npm/cli/releases/tag/v9.0.0-pre.4
    
    Release details...
    

@github-actions github-actions bot force-pushed the release-please--branches--latest branch 14 times, most recently from c1223c9 to 3f098a7 Compare October 5, 2022 18:34
@github-actions github-actions bot force-pushed the release-please--branches--latest branch from 3f098a7 to 9fb08cc Compare October 5, 2022 18:35
@wraithgar wraithgar merged commit 37bf6d3 into latest Oct 5, 2022
@wraithgar wraithgar deleted the release-please--branches--latest branch October 5, 2022 20:30
@github-actions
Copy link
Contributor Author

github-actions bot commented Oct 5, 2022

@github-actions
Copy link
Contributor Author

github-actions bot commented Oct 5, 2022

@github-actions
Copy link
Contributor Author

github-actions bot commented Oct 5, 2022

@github-actions
Copy link
Contributor Author

github-actions bot commented Oct 5, 2022

@github-actions
Copy link
Contributor Author

github-actions bot commented Oct 5, 2022

@github-actions
Copy link
Contributor Author

github-actions bot commented Oct 5, 2022

@github-actions
Copy link
Contributor Author

github-actions bot commented Oct 5, 2022

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