Bump softprops/action-gh-release from 1 to 2

[dependabot]

Bumps softprops/action-gh-release from 1 to 2.

Release notes

Sourced from softprops/action-gh-release's releases.

v2.0.0

• update actions.yml declaration to node20 to address warnings

Changelog

Sourced from softprops/action-gh-release's changelog.

0.1.12

• fix bug leading to empty strings subsituted for inputs users don't provide breaking api calls #144

Commits

• 9d7c94c build
• 6ffed59 followup to #417 (#425)
• 1ce812a package script for updating git tag
• 3198ee1 prep release
• 7ee8e06 declare an update docs for make_latest input (#419)
• d99959e prep release
• 0e39c67 make pattern error opt in (#417)
• 20e085c kick off 2.0.1 release
• 9f5c4d3 update changelog
• 0bea76b Add support for make_latest property (#304)
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[mikefarah]

@copilot are there any risks or incompatibilities with this change?

[Copilot]

Pull request overview

This PR upgrades the softprops/action-gh-release GitHub Action from version 1 to version 2, which updates the action to use Node.js 20 and addresses deprecation warnings in GitHub Actions workflows.

Changes:

• Updated softprops/action-gh-release from v1 to v2 in the release workflow

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[mikefarah]

@copilot are there any risks or incompatibilities with this change?

[mikefarah]

@copilot are there any risks or incompatibilities with this change?

[Copilot]

@copilot are there any risks or incompatibilities with this change?

For this specific workflow the risks are minimal:

1. Node.js runtime – the primary change in v2 is upgrading the action's runtime from Node 16 to Node 20. This avoids deprecation warnings on GitHub-hosted runners and has no impact on workflow logic.

2. files: build/* glob – glob matching was improved in v2, but a simple build/* pattern is handled identically.

3. draft: true – draft creation behaviour is unchanged for the straightforward draft: true flag.

4. fail_on_unmatched_files: true – this input is still fully supported in v2.

5. Authentication – v2 gives priority to an explicit token input over the implicit GITHUB_TOKEN. Since this workflow doesn't set token: explicitly, the action falls back to GITHUB_TOKEN automatically, so no auth change is needed.

6. No consumed outputs – the workflow doesn't read any outputs from this step, so the minor structural changes to action outputs in v2 are irrelevant here.

In short, this upgrade is safe to merge as-is. The main benefit is eliminating the Node 16 deprecation warnings that GitHub now surfaces in workflow logs.

@copilot are there any risks or incompatibilities with this change?

For this specific workflow the risks are minimal:

1. Node.js runtime – the primary change in v2 is upgrading the action's runtime from Node 16 to Node 20. This avoids deprecation warnings on GitHub-hosted runners and has no impact on workflow logic.

2. files: build/* glob – glob matching was improved in v2, but a simple build/* pattern is handled identically.

3. draft: true – draft creation behaviour is unchanged for the straightforward draft: true flag.

4. fail_on_unmatched_files: true – this input is still fully supported in v2.

5. Authentication – v2 gives priority to an explicit token input over the implicit GITHUB_TOKEN. Since this workflow doesn't set token: explicitly, the action falls back to GITHUB_TOKEN automatically, so no auth change is needed.

6. No consumed outputs – the workflow doesn't read any outputs from this step, so the minor structural changes to action outputs in v2 are irrelevant here.

In short, this upgrade is safe to merge as-is. The main benefit is eliminating the Node 16 deprecation warnings that GitHub now surfaces in workflow logs.

@copilot are there any risks or incompatibilities with this change?

For this specific workflow the risks are minimal:

1. Node.js runtime – the primary change in v2 is upgrading the action's runtime from Node 16 to Node 20. This avoids deprecation warnings on GitHub-hosted runners and has no impact on workflow logic.

2. files: build/* glob – glob matching was improved in v2, but a simple build/* pattern is handled identically.

3. draft: true – draft creation behaviour is unchanged for the straightforward draft: true flag.

4. fail_on_unmatched_files: true – this input is still fully supported in v2.

5. Authentication – v2 gives priority to an explicit token input over the implicit GITHUB_TOKEN. Since this workflow doesn't set token: explicitly, the action falls back to GITHUB_TOKEN automatically, so no auth change is needed.

6. No consumed outputs – the workflow doesn't read any outputs from this step, so the minor structural changes to action outputs in v2 are irrelevant here.

In short, this upgrade is safe to merge as-is. The main benefit is eliminating the Node 16 deprecation warnings that GitHub now surfaces in workflow logs.