Skip to content

Version number is not semver compliant and crate version string is outdated #9

@rymdbar

Description

@rymdbar

Currently 3.13.2.2 is the most recent version tag of this git repository.

It would be ideal if version numbers were kept in compliance with semver and mirrored in Cargo.toml. Not only would that make it easier to find and figure out which version is in use, but it would also make the version number available at build-time in $CARGO_PKG_VERSION.

As the tags with an additional dot seems to only change files arguably not within the actual project sources, maybe they could be tagged as something similar to 3.13.2msgh2 in the future to indicate they only touch Microsoft GitHub Actions?

Had this been my project, I would likely have added a guard either at build-time or as a git-hook to ensure the different version strings were kept up to date with each-other.

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