Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Jun 22, 2023

🤖 I have created a release beep boop

7.5.3 (2023-06-22)

Bug Fixes

Documentation


This PR was generated with Release Please. See documentation.

@github-actions github-actions bot requested a review from a team as a code owner June 22, 2023 20:07
@github-actions
Copy link
Contributor Author

github-actions bot commented Jun 22, 2023

Release Manager

Release workflow run: https://github.com/npm/node-semver/actions/runs/5350581410

Force CI to Update 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 update this PR, run this command:

gh workflow run release.yml -r main -R npm/node-semver -f release-pr=572 

Release Checklist for v7.5.3

  • 1. Merge release PR 🚨 Merging this will auto publish 🚨

    gh pr merge 572 -R npm/node-semver --rebase
  • 2. 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 -R npm/node-semver $(gh run list -R npm/node-semver -w release -b main -L 1 --json databaseId -q ".[0].databaseId") 
@github-actions github-actions bot force-pushed the release-please--branches--main branch 2 times, most recently from 2000339 to 3fb4490 Compare June 22, 2023 21:42
@github-actions github-actions bot force-pushed the release-please--branches--main branch from 3fb4490 to 2471244 Compare June 22, 2023 21:43
@lukekarrys lukekarrys merged commit 7fdf1ef into main Jun 22, 2023
@lukekarrys lukekarrys deleted the release-please--branches--main branch June 22, 2023 21:50
@github-actions
Copy link
Contributor Author

github-actions bot commented Jun 22, 2023

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

1 participant