semantic-release-action icon indicating copy to clipboard operation
semantic-release-action copied to clipboard

GitHub Action for Semantic Release

Results 30 semantic-release-action issues
Sort by recently updated
recently updated
newest added

My current CI produces and uploads 2 artifacts from two folders in the repo. One is a core package and the other is optional, containing extra stuff for demo testing...

**Describe the bug** We're using your semantic release action (thanks!) in a release workflow which has been working fine though we've had a blip where the following error was thrown....

**Describe the bug** Tags are not cleared on failure **Workflow** ```yaml - name: Checkout uses: actions/checkout@v1 - name: Semantic Release id: semantic uses: cycjimmy/semantic-release-action@v2 env: GH_TOKEN: ${{ secrets.GH_TOKEN }} with:...

I want to write `npm run format` before semantic-release-bot commits the release tag. How can I do that?

**Describe the bug** A clear and concise description of what the bug is. After releasing several bug fixes, the CI and bot still seem to be releasing the same version...

**Describe the bug** See https://github.com/semantic-release/semantic-release/issues/1581 **Workflow** N/A **Expected behavior** Repository with `main` branch is released automatically. **Additional context** Repository with `main` branch is not released automatically.

**Describe the bug** I'm using `semantic-release` to release new package versions. It worked ~17 days ago just fine. - This only fails when used in the self-hosted runner on Mac...

**Describe the bug** I ran semantic-release on the master branch, but the release fail. The reason is the following. ``` [5:34:45 AM] [semantic-release] › ℹ Running semantic-release version 19.0.3 [5:34:46...

**Describe the bug** When using `workflow_run` in a workflow that uses `semantic-release-action`, semantic release will reference the wrong branch and git tags. **Workflow** I have 1 release branch (main) and...

**Describe the bug** Documentation says that passing a DRY_RUN of true will over-ride the configuration file and perform a dry run. I've tried specifying it as true and it still...