You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tagging is generally used to capture a point in history that is used for a marked version release (i.e. v4.6.1). You don't need include specific commit hash in artefact name.
Could you do not use commit hash in releases artefact names? Thanks!
The text was updated successfully, but these errors were encountered:
Hello. Artefact release names changed.
Before: raven-4.3.2.0-x86_64-linux-gnu.tar.gz
Commit hash included into artefact name
After: raven-4.6.1-7864c39c2-x86_64-linux-gnu.tar.gz
This changes affect download automation
Tagging is generally used to capture a point in history that is used for a marked version release (i.e. v4.6.1). You don't need include specific commit hash in artefact name.
Could you do not use commit hash in releases artefact names? Thanks!
The text was updated successfully, but these errors were encountered: