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
The release process is based on Git tags and makes use of evolution-gaming/scala-github-actions which uses sbt-dynver to automatically obtain the version from the latest Git tag. The flow is defined in .github/workflows/release.yml.
A typical release process is as follows:
Create and push a new Git tag. The version should be in the format vX.Y.Z (example: v4.1.0). Example: git tag v4.1.0 && git push origin v4.1.0
On success, a new GitHub release is automatically created with a calculated diff and auto-generated release notes.
You can see it on Releases page, change the description if needed
On failure, the tag is deleted from the remote repository. Please note that your local tag isn't deleted, so if the failure
is recoverable then you can delete the local tag and try again (an example of unrecoverable failure is successfully
publishing only a few of the artifacts to Artifactory which means a new attempt would fail since Artifactory doesn't allow
overwriting its contents)