chore(deps): bump softprops/action-gh-release from 2 to 3

[dependabot]

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

Release notes

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

v3.0.0

3.0.0 is a major release that moves the action runtime from Node 20 to Node 24. Use v3 on GitHub-hosted runners and self-hosted fleets that already support the Node 24 Actions runtime. If you still need the last Node 20-compatible line, stay on v2.6.2.

What's Changed

Other Changes 🔄

• Move the action runtime and bundle target to Node 24
• Update @types/node to the Node 24 line and allow future Dependabot updates
• Keep the floating major tag on v3; v2 remains pinned to the latest 2.x release

v2.6.2

What's Changed

Other Changes 🔄

• chore(deps): bump picomatch from 4.0.3 to 4.0.4 by @​dependabot[bot] in softprops/action-gh-release#775
• chore(deps): bump brace-expansion from 5.0.4 to 5.0.5 by @​dependabot[bot] in softprops/action-gh-release#777
• chore(deps): bump vite from 8.0.0 to 8.0.5 by @​dependabot[bot] in softprops/action-gh-release#781

Full Changelog: softprops/action-gh-release@v2...v2.6.2

v2.6.1

2.6.1 is a patch release focused on restoring linked discussion thread creation when discussion_category_name is set. It fixes [#764](https://github.com/softprops/action-gh-release/issues/764), where the draft-first publish flow stopped carrying the discussion category through the final publish step.

If you still hit an issue after upgrading, please open a report with the bug template and include a minimal repro or sanitized workflow snippet where possible.

What's Changed

Bug fixes 🐛

• fix: preserve discussion category on publish by @​chenrui333 in softprops/action-gh-release#765

v2.6.0

2.6.0 is a minor release centered on previous_tag support for generate_release_notes, which lets workflows pin GitHub's comparison base explicitly instead of relying on the default range. It also includes the recent concurrent asset upload recovery fix, a working_directory docs sync, a checked-bundle freshness guard for maintainers, and clearer immutable-prerelease guidance where GitHub platform behavior imposes constraints on how prerelease asset uploads can be published.

If you still hit an issue after upgrading, please open a report with the bug template and include a minimal repro or sanitized workflow snippet where possible.

What's Changed

... (truncated)

Changelog

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

0.1.13

• fix issue with multiple runs concatenating release bodies #145

Commits

• 3d0d988 release 3.0.2 (#818)
• 7e13ed4 fix: clarify release creation 404 errors (#817)
• e6c70a5 fix: replace existing release assets on Gitea (#816)
• f345337 fix: publish existing draft releases as prereleases (#801)
• d8a89a2 fix: upload small checksum assets reliably (#815)
• 45ece40 chore(deps): remove unused TypeScript tooling (#814)
• f6b913c feat: improve release error reporting and test coverage (#813)
• 15f193d chore(deps): upgrade TypeScript to 7 (#812)
• cc8268d chore(deps): bump actions/checkout in the github-actions group (#810)
• fd0ed1e chore(deps): bump the npm group with 3 updates (#811)
• Additional commits viewable in compare view

[mrnicholasbcarter-code]

@dependabot recreate

[mrnicholasbcarter-code]

Evidence: this dependency-only PR inherits the repository baseline: Ruff reports four violations in tests/test_coverage_gap.py before tests run. The repository also has an in-progress package rebrand boundary (metadata says verdict-risk while code remains trade_risk_engine). This red update must not merge; package-boundary and lint fixes belong in a dedicated PR.

[mrnicholasbcarter-code]

Closing the red dependency update. CI audit shows the shared baseline fails Ruff on tests/test_coverage_gap.py, and the repository has an unresolved metadata/package boundary (verdict-risk vs trade_risk_engine). Repair that boundary and lint baseline in a dedicated PR first.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.