semantic-release / semantic-release/exec
fails when ${nextRelease.notes} contains quotes
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 164
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
I'm trying to pass ${nextRelease.notes} to an exec step but it fails if the notes contains quotes with Unterminated quoted string.
For exemple, I have a commit with message
feat(test): test"'
with s "' pecial characters
The espaceCommand seems to have single quote escaped but not quotes.
escapedCommand: `'./templates/azdo/summary.sh "## [1.1.0](https://dev.azure.com/_git/containerapps-sample/branchCompare?baseVersion=GTrelease/1.0.1&targetVersion=GTrelease/1.1.0&_a=commits) (2025-06-07)\\n\\n\\n### Features\\n\\n* test ([e21ff0f]([https://dev.azure.com/_git/containerapps-sample/commit/e21ff0f4bc00a00d2e87d10cdbb966db176c2ed8))\\n*](https://dev.azure.com/_git/containerapps-sample/commit/e21ff0f4bc00a00d2e87d10cdbb966db176c2ed8))//n*) **test:** test"'\\'' ([1e411df]([https://dev.azure.com/_git/containerapps-sample/commit/1e411df9eb41669aab917f2c9b2b9ea48b9e61f0))\\n\\n"\\n'`,](https://dev.azure.com/_git/containerapps-sample/commit/1e411df9eb41669aab917f2c9b2b9ea48b9e61f0))//n//n%22//n'%60,)
The plugin is configured with this yaml fragment
- - '@semantic-release/exec'
- publishCmd: |
./summary.sh "${nextRelease.notes}"
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the @semantic-release/exec publishCmd configuration and the escapedCommand output shown in the issue, then reproduce the failure using release notes containing both single and double quotes. The work is done when the generated exec command runs successfully without an unterminated quoted string for those notes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, shell
- Domain
- cli, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100