chore: release 7.5.4 #586
Merged
chore: release 7.5.4 #586
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=80&v=4){kind=small}
Release ManagerRelease workflow run: https://github.com/npm/node-semver/actions/runs/5489419204 Force CI to Update This ReleaseThis PR will be updated and CI will run for every non- Release Checklist for v7.5.4
|
github-actions bot force-pushed the release-please--branches--main branch 2 times, most recently from a9726d4 to 5d26fc1 Compare 
github-actions bot force-pushed the release-please--branches--main branch from 5d26fc1 to 12d5e01 Compare 
lukekarrys approved these changes Jul 7, 2023
Release Workflow
|
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
7.5.4 (2023-07-07)
Bug Fixes
cc6fde2#588 trim each range set before parsing (@lukekarrys)99d8287#583 correctly parse long build ids as valid (fix: correctly parse long build ids as valid #583) (@lukekarrys)This PR was generated with Release Please. See documentation.