feat: adds fixName step for publishing #145
Merged
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
9fcc292 to
8e50075
Compare
wraithgar
reviewed
May 16, 2025
wraithgar
reviewed
May 16, 2025
wraithgar
reviewed
May 16, 2025
c90678b to
f9d9155
Compare
wraithgar
reviewed
May 19, 2025
f9d9155 to
7c1b81f
Compare
wraithgar
approved these changes
May 21, 2025
Merged
wraithgar
pushed a commit
that referenced
this pull request
May 21, 2025
🤖 I have created a release *beep* *boop* --- ## [6.2.0](v6.1.1...v6.2.0) (2025-05-21) ### Features * [`228539f`](228539f) [#145](#145) adds fixName step for publishing (#145) (@owlstronaut) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
npm/statusboard#933