actions/softprops__action-gh-release
1
0
Fork 0
mirror of https://gh-proxy.org/https://github.com/softprops/action-gh-release.git synced 2026-07-15 23:13:02 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
master
softprops__action-gh-release/CHANGELOG.md
T
Rui Chen d100e75a45 docs: mark v2 as unsupported (#821) 
Signed-off-by: Rui Chen <rui@chenrui.dev>
2026-07-13 13:15:35 -04:00

22 KiB
Raw Permalink Blame History

3.0.2

3.0.2 is a patch release focused on release reliability and compatibility. It reuses existing draft releases when publishing prereleases, supports replacing release assets on Gitea, hardens streamed asset uploads, and provides clearer release-creation diagnostics. It also includes TypeScript, coverage, and tooling maintenance merged since 3.0.1.

This release fixes #795, #438, and #803. The upload transport hardening covers the historical failure reported in #790, although current hosted Node 24 runners did not reproduce it naturally. The diagnostics work is related to #786 and does not claim a reproducible release-creation fix.

What's Changed

Exciting New Features 🎉

Bug fixes 🐛

Other Changes 🔄

3.0.1

  • maintenance release with updated dependencies

3.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. v2.6.2 was the final Node 20-compatible release and is no longer maintained or supported.

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; freeze v2 at the final v2.6.2 release

2.6.2

2.6.2 is the final v2 release and is no longer maintained or supported. Upgrade to v3 for the supported Node 24 runtime and current fixes.

What's Changed

Other Changes 🔄

2.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, 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 🐛

2.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

Exciting New Features 🎉

Bug fixes 🐛

Other Changes 🔄

2.5.3

2.5.3 is a patch release focused on the remaining path-handling and release-selection bugs uncovered after 2.5.2. It fixes #639, #571, #280, #614, #311, #403, and #368. It also adds documentation clarifications for #541, #645, #542, #393, and #411, where the current behavior is either usage-sensitive or constrained by GitHub platform limits rather than an action-side runtime bug.

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 🐛

Other Changes 🔄

2.5.2

2.5.2 is a patch release focused on the remaining release-creation and prerelease regressions in the 2.5.x bug-fix cycle. It fixes #705, fixes #708, fixes #740, fixes #741, and fixes #722. Regression testing covers the shared-tag race, prerelease event behavior, dotfile asset labels, same-filename concurrent uploads, and blocked-tag cleanup behavior.

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 🐛

2.5.1

2.5.1 is a patch release focused on regressions introduced in 2.5.0 and on release lookup reliability. It fixes #713, addresses #703, and fixes #724. Regression testing shows that current master no longer reproduces the finalize-race behavior reported in #704 and #709.

What's Changed

Bug fixes 🐛

Other Changes 🔄

2.5.0

What's Changed

Exciting New Features 🎉

Other Changes 🔄

  • dependency updates

2.4.2

What's Changed

Exciting New Features 🎉

Other Changes 🔄

  • dependency updates

2.4.1

What's Changed

Other Changes 🔄

2.4.0

What's Changed

Exciting New Features 🎉

2.3.4

What's Changed

Bug fixes 🐛

Other Changes 🔄

  • dependency updates

2.3.3

What's Changed

Exciting New Features 🎉

Other Changes 🔄

  • dependency updates

2.3.2

  • fix: revert fs readableWebStream change

2.3.1

Bug fixes 🐛

2.3.0

  • Migrate from jest to vitest
  • Replace mime with mime-types
  • Bump to use node 24
  • Dependency updates

2.2.2

What's Changed

Bug fixes 🐛

Other Changes 🔄

2.2.1

What's Changed

Bug fixes 🐛

Other Changes 🔄

2.2.0

What's Changed

Exciting New Features 🎉

Bug fixes 🐛

Other Changes 🔄

2.1.0

What's Changed

Exciting New Features 🎉

Other Changes 🔄

2.0.9

  • maintenance release with updated dependencies

2.0.8

Other Changes 🔄

2.0.7

Bug fixes 🐛

Other Changes 🔄

2.0.6

  • maintenance release with updated dependencies

2.0.5

  • Factor in file names with spaces when upserting files #446 via @MystiPanda
  • Improvements to error handling #449 via @till

2.0.4

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

2.0.0

  • 2.0.0!? this release corrects a disjunction between git tag versions used in the marketplace and the versions listed in 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

0.1.14

  • provides a new workflow input option generate_release_notes which when set to true will automatically generate release notes for you based on GitHub activity #179. Please see the GitHub docs for this feature for more information

0.1.13

  • fix issue with multiple runs concatenating release bodies #145

0.1.12

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

0.1.11

  • better error message on release create failed #143

0.1.10

  • fixed error message formatting for file uploads

0.1.9

  • add support for linking release to GitHub discussion #136

0.1.8

  • address recent warnings in assert upload api as well as introduce asset upload overrides, allowing for multiple runs for the same release with the same named asserts #134
  • fix backwards compatibility with GITHUB_TOKEN resolution. GITHUB_TOKEN is now resolved first from an env variable and then from an input #133
  • trim white space in provided tag_name #130

0.1.7

  • allow creating draft releases without a tag #95
  • Set default token for simpler setup #83
  • fix regression with action yml #126

0.1.6

This is a release catch up have a hiatus. Future releases will happen more frequently

  • Add 'fail_on_unmatched_files' input, useful for catching cases where your files input does not actually match what you expect #55
  • Add repository input, useful for creating a release in an external repository #61
  • Add release id to outputs, useful for referring to release in workflow steps following the step that uses this action #60
  • Add upload_url as action output, useful for managing uploads separately #75
  • Support custom target_commitish value, useful to customize the default #76
  • fix body_path input first then fall back on body input. This was the originally documented precedence but was implemented in the opposite order! #85
  • Retain original release info if the keys are not set, useful for filling in blanks for a release you've already started separately #109
  • Limit number of times github api request to create a release is retried, useful for avoiding eating up your rate limit and action minutes due to either an invalid token or other circumstance causing the api call to fail #111

0.1.5

  • Added support for specifying tag name #39

0.1.4

  • Added support for updating releases body #36
  • Steps can now access the url of releases with the url output of this Action #28
  • Added basic GitHub API retry support to manage API turbulence #26

0.1.3

  • Fixed where with: body_path was not being used in generated GitHub releases

0.1.2

  • Add support for merging draft releases #16

GitHub's api doesn't explicitly have a way of fetching a draft release by tag name which caused draft releases to appear as separate releases when used in a build matrix. This is now fixed.

  • Add support for newline-delimited asset list #18

GitHub actions inputs don't inherently support lists of things and one might like to append a list of files to include in a release. Previously this was possible using a comma-delimited list of asset path patterns to upload. You can now provide these as a newline delimited list for better readability

- name: Release
  uses: softprops/action-gh-release@v1
  if: startsWith(github.ref, 'refs/tags/')
  with:
    files: |
      filea.txt
      fileb.txt
      filec.txt
  env:
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
  • Add support for prerelease annotated GitHub releases with the new input field with.prerelease: true #19

0.1.1

  • Add support for publishing releases on all supported virtual hosts

You'll need to remove docker:// prefix and use the @v1 action tag

0.1.0

  • Initial release
Reference in New Issue View Git Blame Copy Permalink