Releases: getsentry/action-release
3.4.0
- feat: Add support for setting manual commit range (#291) by @andreiborza
Work in this release was contributed by @trevorkwhite. Thank you for your contribution!
3.3.0
3.2.0
Various fixes & improvements
- chore: Set docker tag for master [skip ci] (e834095) by @getsantry[bot]
- feat: Bump to node 20.19.2 (#284) by @andreiborza
- chore: Set docker tag for master [skip ci] (ec695e2) by @getsantry[bot]
3.1.2
- fix: Preserve existing Node version on macOS and Windows runners (#280) by @andreiborza
3.1.1
- fix: Only pass
urlPrefixto sentry-cli if it's not empty (#275) by @andreiborza
3.1.0
- feat: Add
releaseandrelease_prefixin favor ofversionandversion_prefix(#273) by @andreiborza
Input parameter version has been deprecated and will be removed in a future version in favor of a newly introduced release parameter.
Input parameter version_prefix has been deprecated and will be removed in a future version in favor of a newly introduced release_prefix parameter.
3.0.0
Version 3.0.0 contains breaking changes:
- feat(sourcemaps)!: Enable injecting debug ids by default (#272) by @andreiborza
The action now automatically injects Debug IDs into your JavaScript source files and source maps to ensure your stacktraces can be
properly un-minified.
This is a breaking change as it modifies your source files. You can disable this behavior by setting inject: false:
- uses: getsentry/action-release@v3
with:
environment: 'production'
sourcemaps: './dist'
inject: falseRead more about Artifact Bundles and Debug IDs here.
1.11.0
- feat: Use hybrid docker/composite action approach (#265) by @andreiborza
After receiving user feedback both on runtime and compatibility issues for 1.10.0
the action has been reworked to use a Docker based approach on Linux runners, mimicking
< 1.9.0 versions, while Mac OS and Windows runners will follow the 1.10.0 approach
of installing @sentry/cli in the run step.
1.10.5
Various fixes & improvements
- fix: Mark
GITHUB_WORKSPACEa safe git directory (#260) by @andreiborza
2.0.0
Note
This release contains no changes over v1.10.4 and is just meant to unblock users that have upgraded to v2 before.
We recommend pinning to v1.
Last week we pushed a v2 branch that triggered dependabot which treated it as a release.
This was not meant to be a release, but many users have upgraded to v2.
This release will help unblock users that have upgraded to v2.
Please see: #258