chore: fix npm release script when its running on a multi line commit message #1676
Conversation
This file contains 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
… message The release script tried to put a multiline string into an env var which resulted in an error. Now only the first line of the commit message is kept. This was causing an issue when trying to do a manual NPM release from a branch
|
balzss
approved these changes
Sep 12, 2024
joyenjoyer
approved these changes
Sep 13, 2024
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.
The release script tried to put a multiline string into an env var which resulted in an error. Now only the first line of the commit message is kept.
This was causing an issue when trying to do a manual NPM release from a branch e.g. https://github.com/instructure/instructure-ui/actions/runs/10836188427/job/30069387696