Bump getsentry/action-release from 3.0.0 to 3.1.0

[dependabot]

Bumps getsentry/action-release from 3.0.0 to 3.1.0.

Release notes

Sourced from getsentry/action-release's releases.

3.1.0

• feat: Add release and release_prefix in favor of version and version_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.

Changelog

Sourced from getsentry/action-release's changelog.

Changelog

3.1.0

• feat: Add release and release_prefix in favor of version and version_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: false

Read 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_WORKSPACE a 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.

... (truncated)

Commits

• fa24763 release: 3.1.0
• 3d9b620 chore: Set docker tag for master [skip ci]
• 40ae96f meta(changelog): Update changelog for 3.1.0 (#274)
• 647ee93 chore: Set docker tag for master [skip ci]
• 7711b5c feat: Add release and release_prefix in favor of version and `version_p...
• 4e3a28f chore: Set docker tag for master [skip ci]
• 059f347 Merge branch 'release/3.0.0'
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)