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 5.7.3 #660

Closed

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Dec 4, 2023

🤖 I have created a release beep boop

5.7.3 (2024-04-21)

Chores


This PR was generated with Release Please. See documentation.

Copy link
Contributor Author

github-actions bot commented Dec 4, 2023

Release Manager

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

Release Checklist for v5.7.3

  • 1. Approve this PR

    gh pr review 660 -R npm/node-semver --approve
  • 2. Merge release PR 🚨 Merging this will auto publish 🚨

    gh pr merge 660 -R npm/node-semver --squash
  • 3. 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 release/v5 -L 1 --json databaseId -q ".[0].databaseId")

@github-actions github-actions bot force-pushed the release-please--branches--release/v5 branch 2 times, most recently from 00eca70 to 3e9da1a Compare December 7, 2023 22:35
@ljharb
Copy link

ljharb commented Dec 7, 2023

this release seems to only contain template-oss updates?

@github-actions github-actions bot force-pushed the release-please--branches--release/v5 branch from 3e9da1a to 71dc4c5 Compare April 21, 2024 16:40
@github-actions github-actions bot force-pushed the release-please--branches--release/v5 branch from 71dc4c5 to 07db06d Compare April 21, 2024 16:41
@lukekarrys lukekarrys closed this May 3, 2024
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.

2 participants