Bump softprops/action-gh-release from 0.1.14 to 2.0.4

[dependabot]

Bumps softprops/action-gh-release from 0.1.14 to 2.0.4.

Release notes

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

v2.0.4

• Minor follow up to #417. #425

v2.0.2

• Revisit approach to #384 making unresolved pattern failures opt-in #417

v2.0.1

• Add support for make_latest property softprops/action-gh-release#304 via @​samueljseay
• Fail run if files setting contains invalid patterns softprops/action-gh-release#384 via @​rpdelaney
• Add support for proxy env variables (don't use node-fetch) softprops/action-gh-release#386 via @​timor-raiman
• Suppress confusing warning when input_files is empty softprops/action-gh-release#389 via @​Drowze

v2.0.0

• update actions.yml declaration to node20 to address warnings

v0.1.15

update actions.yml declaration to node16 to address warnings upgrade dependencies

Changelog

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

2.0.4

• Minor follow up to #417. #425

2.0.3

• Declare make_latest as an input field in action.yml #419

2.0.2

• Revisit approach to #384 making unresolved pattern failures opt-in #417

2.0.1

• Add support for make_latest property #304 via @​samueljseay
• Fail run if files setting contains invalid patterns #384 via @​rpdelaney
• Add support for proxy env variables (don't use node-fetch) #386 via @​timor-raiman
• Suppress confusing warning when input_files is empty #389 via @​Drowze

2.0.0

• 2.0.0!? this release corrects a disjunction between git tag versions used in the marketplace and versions list this file. Previous versions should have really been 1.*. Going forward this should be better aligned.
• Upgrade action.yml declaration to node20 to address deprecations

0.1.15

• Upgrade to action.yml declaration to node16 to address deprecations
• Upgrade dependencies
• Add asset output as a JSON array containing information about the uploaded assets

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

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)

[runtime-shady-backroom]

@dependabot ignore this minor version

[dependabot]

OK, I won't notify you about version 2.0.x again, unless you re-open this PR.

[runtime-shady-backroom]

Softprops versions greater than 0.1.14 have a regression which break my build on windows hosts. I've confirmed this is NOT fixed yet in 2.0.4.