Bump getsentry/action-release from 1 to 2

[dependabot]

Bumps getsentry/action-release from 1 to 2.

Release notes

Sourced from getsentry/action-release's releases.

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

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

1.10.4

Various fixes & improvements

• fix(action): Use action/setup-node instead of unofficial volta action (#256) by @​andreiborza

1.10.3

Various fixes & improvements

• fix(ci): Use volta to ensure node and npm are available (#255) by @​andreiborza

1.10.2

• fix(action): Ensure working directory always starts out at repo root (#250)
• fix(action): Use npm instead of yarn to install sentry-cli (#251)

1.10.1

This release contains changes concerning maintainers of the repo and has no user-facing changes.

v1.10.0

• feat(action): Support macos and windows runners
  We now publish a composite action that runs on all runners. Actions can now be properly versioned, allowing pinning versions from here on out.

v1.9.0

What's Changed

... (truncated)

Changelog

Sourced from getsentry/action-release's changelog.

Changelog

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.

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: #209

1.10.4

Various fixes & improvements

• fix(action): Use action/setup-node instead of unofficial volta action (#256) by @​andreiborza

1.10.3

Various fixes & improvements

• fix(ci): Use volta to ensure node and npm are available (#255) by @​andreiborza

1.10.2

• fix(action): Ensure working directory always starts out at repo root (#250)
• fix(action): Use npm instead of yarn to install sentry-cli (#251)

1.10.1

... (truncated)

Commits

• 89d6259 fix: Ensure action's js builds after bumping version in craft-pre-release #245
• 5b9cb24 fix: Ensure action's js builds after bumping version in craft-pre-release (#244)
• 0a5a3ea Merge branch 'release/1.10.0'
• 4b50052 release: 1.10.0
• 24fbab5 chore(action): Rework action to be a composite action (#243)
• 5d153c1 fix(craft): Fix craft target to publish to github registry (#242)
• bff9869 chore(release): Unset artifactProvider in craft (#241)
• 83f0898 meta(release): First craft release (#240)
• 5e6fd0e chore(release): Add craft publish workflow (#238)
• f5a213d feat(telemetry): Track usage of finalize (#236)
• Additional commits viewable 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)