Skip to content

Semantic release isn't publishing dist files when a new version is released #153

@jhackett1

Description

@jhackett1

semantic-release should build css and js files and commit them in the dist directory whenever it releases a new version to npm:

      [
        "@semantic-release/git",
        {
          "assets": [
            "dist/**/*.{js,css}",
            "package.json",
            "CHANGELOG.md"
          ],
          "message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
        }
      ]

this isn't happening.

it is committing new changelog.md and package.json files, so something about committing the dist files in particular is causing trouble.

investigate:

  • config syntax
  • are build files being pushed to npm but not git? or not at all?
  • what happens during a dry run?

Metadata

Metadata

Assignees

Labels

bugSomething isn't workinggood first issueGood for newcomershelp wantedExtra attention is needed

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions