We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Record the Git hash of the release's tag in the libraries index.
🙂 It will be possible to conclusively ascertain which point in a library's Git revision history corresponds to a release in the index.
The only versioning information available about a library release is the version number.
It is a common problem for library maintainers to forget to update the value of the version property in the library metadata before pushing a Git tag.
version
Significant effort is made in the libraries-repository-engine codebase to process Git tags in ascending chronological order, but this is not guaranteed.
Library maintainers sometimes later move published tags, or delete tags.
🙁 There may be ambiguity regarding exactly which point in a library's Git revision history corresponds to a release in the index.
19f9d91
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Uh oh!
There was an error while loading. Please reload this page.
Describe the request
Record the Git hash of the release's tag in the libraries index.
🙂 It will be possible to conclusively ascertain which point in a library's Git revision history corresponds to a release in the index.
Describe the current behavior
The only versioning information available about a library release is the version number.
It is a common problem for library maintainers to forget to update the value of the
version
property in the library metadata before pushing a Git tag.Significant effort is made in the libraries-repository-engine codebase to process Git tags in ascending chronological order, but this is not guaranteed.
Library maintainers sometimes later move published tags, or delete tags.
🙁 There may be ambiguity regarding exactly which point in a library's Git revision history corresponds to a release in the index.
libraries-repository-engine version
19f9d91
Issue checklist
The text was updated successfully, but these errors were encountered: