semantic-release / semantic-release/github
Can I use the templates in asset's path config?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 534
- Forks
- 150
- Avg merge
- 1m
- Merged PRs (30d)
- 3
Description
Hi there, thanks for the great project!
I have the following files:
dist/file1-v1.0.0.zip
dist/file1-v1.0.1.zip
dist/file1-v1.1.0.zip
...etc
I wanted to attach the last generated file on the release in question. For that, I had this configuration:
[
"@semantic-release/github",
{
"assets": "dist/*.zip"
}
]
With the config above, all my files in dist/ folder were getting attached to each release in Github's release page. So far so good, it was working as expected and it was a silly mistake of mine.
Then I tried to fix it by doing the following:
[
"@semantic-release/github",
{
"assets": "dist/*${nextRelease.version}.zip"
}
]
But it didn't work -- no assets were attached to the next release. Am I missing something? Are templates even supported in path?
Thank you!
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 by tracing how the @semantic-release/github configuration resolves the assets path, especially the dist/*${nextRelease.version}.zip example. Check whether the path supports release-version templates and how matching assets are selected. Done means the versioned zip is attached to the GitHub release without attaching older files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100