v6.1.0

Added

• Added latest release management.

Latest release management

This action can now manage when published releases are set as the latest release for the repo.

By default, releases created by this action will be marked as the latest release if they are newly created, non-draft, stable releases. Other strategies for when to set the latest release can be configured via the makeLatest action input or configuration option. Strategies include:

• if-new: Set the release as latest if it is newly created. This is the default strategy.
• semver: Set the release as latest if it's a SemVer version greater than the current latest release.
• legacy: Defer to GitHub's legacy behavior for choosing latest releases.
• always: Always set the release as latest, even if it's not newly created.
• never: Never set the release as latest.

v6

This tag currently points to v6.1.0

v6.0.1

Fixed

• Bumped schema version numbers to match the major version number.
• Updated examples in the docs to refer to the latest version.

v6.0.0

Changed

• This action now runs on the node24 runner instead of node20. If you are using this action on GitHub Enterprise Server, you will need to ensure your runners support node24 before upgrading to this version.

v5.4.0

Added

• Added config file schema support.

Config file schema support

The configuration schema is now published at: https://ghalactic.github.io/github-release-from-tag/schema/config.v5.schema.json

Your editor might be able to use this schema to provide autocompletion and validation for your configuration file. For example, if you're using the YAML extension for Visual Studio Code, you can add the following header to your configuration file to enable schema support:

# yaml-language-server: $schema=https://ghalactic.github.io/github-release-from-tag/schema/config.v5.schema.json
assets:
  - path: assets/text/file-a.txt
  - path: assets/json/file-b.json
    optional: true
    name: custom-name-b.json
    label: Label for file-b.json

In case your editor supports using a $schema property directly in the YAML file, the schema has been relaxed to allow this as well:

$schema: https://ghalactic.github.io/github-release-from-tag/schema/config.v5.schema.json
assets:
  - path: assets/text/file-a.txt
  - path: assets/json/file-b.json
    optional: true
    name: custom-name-b.json
    label: Label for file-b.json

Fixed

• Fixed parsing of empty configuration files with comments.

v5

This tag currently points to v5.4.0

v5.3.0

Added

• Markdown heading anchors are now added to release bodies.

Markdown heading anchors

Anchors are now added to headings in the release body. This makes it possible to link directly to a specific section of the release body, either from within the release body itself, or externally once the release is created. You would probably expect GitHub to do this as a part of its release body rendering, just like it does for READMEs, but surprisingly it doesn't. So, now this action will do it for you.

In order to be able to see that this feature is working, it helps for this page to be really tall. So here's an extremely long cat to help you out:

v5.2.1

Fixed

• Dependency updates.

v5.2.0

Added

• This action now uploads checksum assets when a release has assets associated with it. Checksum assets are files that contain the checksums of the other release assets. This feature is enabled by default, but can be disabled via configuration.
• Asset checksums are now available in the assets output. These checksums are always available, even if the checksum assets feature is disabled.

v5.1.1

Fixed

• Updated example workflow to use the inputs context instead of github.event.inputs. This is now possible because GitHub unified their Actions inputs across manual and reusable workflows.