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

The Original GitHub Action for running semantic-release. Sets output and environment variables for you to use in subsequent actions.

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

As of today, v14 is in Maintenance mode and v16 is the active LTS version. https://nodejs.org/en/about/releases/ Is there a reason you use v12 in the Docker image? Would you mind...

If I were to use an extra plugin that this action doesn't use, by default, it does not install it. Is this expected? Feels like this action could install all...

Allows users to install non-standard plugins and shareable configuration packages for use in their `plugins` and `extends` without having the install those dependencies in their own applications. Closes #168 ###...

I have a workflow running on a GitHub Enterprise runner and need to override certain NPM directories/files like `~/.npm` and `~/.npmrc`. The step below shows the environment variables I use...

When upgrading from v1 to v2, running this action on self-hosted runners causes the cloned repo on the runner to be owned by root, causing subsequent runs of the same...

As mentioned in #174 , it is possible to specify the `pkgRoot` to change the working directory for the `npm` publishing step specifically. However, we have found this doesn't address...

### Related Issue #209 ### Description Adds `working-directory` input which affects how it discovers release config as well as the CWD it passes in to the semantic-release command.

Hi, is it time to upgrade the `semantic-release` package to the latest upstream version? I had a problem recently with using an ESM packaged preset `conventional-changelog-conventionalcommits` Thank you