Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Seems to be updating some files but not others

Open
  • Is something wrong?
#262 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
git, javascript
Domain
release

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.

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?

Dominant language
JavaScript
Stars
340
Forks
75
Avg merge
4h 49m
Merged PRs (30d)
6

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from semantic-release/git

All issues in semantic-release/git

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.