Skip to content

Use a semver-compatible tag for releases #175

@sudoforge

Description

@sudoforge

Currently, this repository creates release tags with a two-character version number, e.g. v17 (the latest at the time of writing).

Ignoring the v prefix, which is noted as "common way in english to indicate it is a version number" by the spec, 17 is not a valid semantic version.

From the spec (v2.0.0):

  1. A normal version number MUST take the form X.Y.Z where X, Y, and Z are non-negative integers, and MUST NOT contain leading zeroes. X is the major version, Y is the minor version, and Z is the patch version. Each element MUST increase numerically. For instance: 1.9.0 -> 1.10.0 -> 1.11.0.

Using a semantic version for release tags improves compatibility of this repository and action with software that expects it, or uses semver to validate version strings, perform automatic updates, etc.

See one such case where this repository's tag structure caused an issue. While this issue describes a warning, note that a primary purpose of this software is to upgrade action references, and to do that, it depends on having a tag that looks like a semantic version string.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions