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

bad substitution when using nextRelease.version or nextRelease.notes #3234

Open
vcrini opened this issue Mar 22, 2024 · 0 comments
Open

bad substitution when using nextRelease.version or nextRelease.notes #3234

vcrini opened this issue Mar 22, 2024 · 0 comments

Comments

@vcrini
Copy link

vcrini commented Mar 22, 2024

Current behavior

In my .releaserc.yml
If I want to customize commit message by removing e.g. [skip ci] with
"message": "chore(release): ${nextRelease.version}\n\n${nextRelease.notes}"
when launching pipeline I obtain

: bad substitution

Expected behavior

it should work since ${nextRelease.*} variables are referenced in documentation

semantic-release version

23.0.5

CI environment

gitlab

Plugins used

semantic-release
@semantic-release/git
@semantic-release/gitlab
@semantic-release/exec

semantic-release configuration

branches:
    - $CI_COMMIT_BRANCH
plugins:
    - "@semantic-release/commit-analyzer"
    - "@semantic-release/release-notes-generator"
    - ["@semantic-release/exec", { "prepareCmd": "bash -x ./prepare.sh ecs-task-definition.json" }]
    - "@semantic-release/gitlab"
    - ["@semantic-release/git", {"assets": ["package.json", "ecs-task-definition.json"], "message": "chore(release): ${nextRelease.version}\n\n${nextRelease.notes}"}]

CI logs

: bad substitution
Cleaning up project directory and file based variables
00:00
ERROR: Job failed: exit code 1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant