Conversation
Add a policy around versioning of this project as well as a Github Action to do this task. Fixes #513 Signed-off-by: Florian Lehner <florian.lehner@elastic.co>
| # Create an annotated tag on the latest commit of the current branch (main) | ||
| git tag -a $TAG_NAME -m "$TAG_NAME" | ||
| # Push the newly created tag to the remote repository | ||
| git push origin $TAG_NAME |
There was a problem hiding this comment.
Should this also create GH releases? (if we do, we could also use the GitHub API to retrieve the last release number and increment that rather than use week numbers?)
There was a problem hiding this comment.
I'm not a fan of GH releases. They don't fit well with git and add some complexity. As the project does not provide artifacts in any way or release notes, I don't see the benefits of GH releases.
Once the project becomes more stable, the use of GH releases should be reconsidered. But for the current development phase, it might be too much overhead.
Co-authored-by: Damien Mathieu <42@dmathieu.com>
I started with weekly auto tagging but figured out that this cadence might be too high. So went down to a monthly schedule. Signed-off-by: Florian Lehner <florian.lehner@elastic.co>
|
One thing I've been thinking, maybe as a next step, is that we probably should run the tests before triggering the release, so we don't release if CI isn't green. |
Co-authored-by: Timo Teräs <timo.teras@iki.fi>
6 participants
Add a policy around versioning of this project as well as a Github Action to do this task.
Fixes #513
This change brings us in compliance with open-telemetry/opentelemetry-collector-releases#976.