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 7.6.0 #661

Merged
merged 1 commit into from
Feb 5, 2024
Merged

chore: release 7.6.0 #661

merged 1 commit into from
Feb 5, 2024

Conversation

github-actions[bot]
Copy link
Contributor

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

🤖 I have created a release beep boop

7.6.0 (2024-01-31)

Features

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/7733040601

Release Checklist for v7.6.0

  • 1. Approve this PR

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

    gh pr merge 661 -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 main -L 1 --json databaseId -q ".[0].databaseId")

@github-actions github-actions bot force-pushed the release-please--branches--main branch from 207f85e to f71fd5f Compare December 7, 2023 22:33
@ljharb
Copy link

ljharb commented Dec 7, 2023

This release seems to contain nothing that matters for runtime except the readme change?

@github-actions github-actions bot force-pushed the release-please--branches--main branch from f71fd5f to 2279366 Compare December 7, 2023 22:35
@github-actions github-actions bot changed the title chore: release 7.5.5 chore: release 7.6.0 Jan 31, 2024
@github-actions github-actions bot force-pushed the release-please--branches--main branch from 2279366 to 6d8dd5c Compare January 31, 2024 22:12
@github-actions github-actions bot force-pushed the release-please--branches--main branch from 6d8dd5c to 94c01ef Compare January 31, 2024 22:13
@wraithgar
Copy link
Member

This release seems to contain nothing that matters for runtime except the readme change?

Now that chore commits are included in the changelog we will see release PRs that happen with no runtime changes, we will simply not land them till there is a change.

@wraithgar wraithgar merged commit 377f709 into main Feb 5, 2024
23 checks passed
@wraithgar wraithgar deleted the release-please--branches--main branch February 5, 2024 17:03
Copy link
Contributor Author

github-actions bot commented Feb 5, 2024

Copy link
Contributor Author

github-actions bot commented Feb 5, 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