semantic-release / semantic-release/git
Seems to be updating some files but not others
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 339
- Forks
- 75
- Avg merge
- 5h 15m
- Merged PRs (30d)
- 6
Description
Hello,
I'm not sure if this is a bug or my own misuse of the plugin.
I'm having an issue with the plugin updating some files on release (changelog and package.json) but not others on this repository.
Part of the release workflow (via a prepublishOnly npm script) is to build some CSS and JS bundles to the /dist folder.
Here's an example of the commit semantic-release is making.
Because my release config looks like this, I'd expect these assets to be commited to the git repo, but this doesn't seem to be happening:
"release": {
"branches": [
"main"
],
"plugins": [
"@semantic-release/commit-analyzer",
"@semantic-release/release-notes-generator",
"@semantic-release/npm",
"@semantic-release/github",
[
"@semantic-release/changelog",
{
"changelogFile": "CHANGELOG.md"
}
],
[
"@semantic-release/git",
{
"assets": [
"dist/**/*.{js,css}",
"package.json",
"CHANGELOG.md"
],
"message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
}
]
]
}
This doesn't seem to be a token issue because it can update the package.json and changelog files successfully.
Could be related to: https://github.com/semantic-release/git/issues/155
Any thoughts?
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 reviewing the release configuration, the prepublishOnly npm script, and the linked example commit to compare which files are produced and committed. Determine whether the configured dist assets should be included alongside package.json and CHANGELOG.md, and document or verify the behavior with a reproducible release case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100