${{ github.sha }}|
| `version_prefix` | Value prepended to auto-generated version. For example "v". |-|
| `set_commits` | Specify whether to set commits for the release. Either "auto" or "skip". |"auto"|
| `projects` | Space-separated list of paths of projects. When omitted, falls back to the environment variable `SENTRY_PROJECT` to determine the project. |-|
| `url_prefix` | Adds a prefix to source map urls after stripping them. |-|
| `strip_common_prefix` | Will remove a common prefix from uploaded filenames. Useful for removing a path that is build-machine-specific. |`false`|
| `working_directory` | Directory to collect sentry release information from. Useful when collecting information from a non-standard checkout directory. |-|
| `disable_telemetry` | The action sends telemetry data and crash reports to Sentry. This helps us improve the action. You can turn this off by setting this flag. |`false`|
| `disable_safe_directory` | The action needs access to the repo it runs in. For that we need to configure git to mark the repo as a safe directory. You can turn this off by setting this flag. |`false`|
### Examples
- Create a new Sentry release for the `production` environment, inject Debug IDs into JavaScript source files and sourcemaps and upload them from the `./dist` directory.
```yaml
- uses: getsentry/action-release@v1
with:
environment: 'production'
inject: true
sourcemaps: './dist'
```
- Create a new Sentry release for the `production` environment of your project at version `v1.0.1`.
```yaml
- uses: getsentry/action-release@v1
with:
environment: 'production'
version: 'v1.0.1'
```
- Create a new Sentry release for [Self-Hosted Sentry](https://develop.sentry.dev/self-hosted/)
```yaml
- uses: getsentry/action-release@v1
env:
SENTRY_URL: https://sentry.example.com/
```
## Contributing
See the [Contributing Guide](./CONTRIBUTING.md).
## License
See the [License File](./LICENSE)
## Troubleshooting
Suggestions and issues can be posted on the repository's
[issues page](https://github.com/getsentry/action-release/issues).
- Forgetting to include the required environment variables
(`SENTRY_AUTH_TOKEN`, `SENTRY_ORG`, and `SENTRY_PROJECT`), yields an error that looks like:
```text
Environment variable SENTRY_ORG is missing an organization slug
```
- Building and running this action locally on an unsupported environment yields an error that looks like:
```text
Syntax error: end of file unexpected (expecting ")")
```
- When adding the action, make sure to first checkout your repo with `actions/checkout@v3`.
Otherwise it could fail at the `propose-version` step with the message:
```text
error: Could not automatically determine release name
```
- In `actions/checkout@v3` the default fetch depth is 1. If you're getting the error message:
```text
error: Could not find the SHA of the previous release in the git history. Increase your git clone depth.
```
you can fetch all history for all branches and tags by setting the `fetch-depth` to zero like so:
```text
- uses: actions/checkout@v3
with:
fetch-depth: 0
```