semantic-release / semantic-release/github
Can't use variables in asset path
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 534
- Forks
- 150
- Avg merge
- 1m
- Merged PRs (30d)
- 3
Description
I'm trying to filter assets to only those that match the new version, e.g.:
plugins:
- '@semantic-release/commit-analyzer'
- '@semantic-release/release-notes-generator'
- - '@semantic-release/github'
- assets:
- {"path": '**/build/libs/*${nextRelease.version}*.jar'}
but I just get an error:
[1:56:24 PM] [semantic-release] [@semantic-release/github] › ✖ The asset **/build/libs/*${nextRelease.version}*.jar cannot be read, and will be ignored.
I tried escaping the braces,
e.g. {"path": '**/build/libs/*$\{nextRelease.version\}*.jar'}
and alternate lodash syntax,
e.g. {"path": '**/build/libs/*<%= nextRelease.version %>*.jar'}
but with the same results.
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
No source files or tests are named. Reproduce the configuration with @semantic-release/github, then trace how the plugin reads and expands asset paths. Done means asset paths can use nextRelease.version, with a test covering the configuration or a clear documented limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100