Align versions.yaml and tune release docs #826
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: ChrsMark <[email protected]>
This was referenced Oct 9, 2025
rogercoll
reviewed
Oct 9, 2025
| 3. Bump up the `module-sets.edit-base.version` in `versions.yaml` i.e. from `v0.20.0` to `v0.21.0` | ||
| (cross check latest version used by [EDOT](https://github.com/elastic/elastic-agent/blob/main/internal/pkg/otel/README.md?plain=1#L30), | ||
| and https://github.com/elastic/opentelemetry-collector-components/tags) | ||
| 4. Set the tag for the following steps with `export $TAG=v0.21.0` |
There was a problem hiding this comment.
Is this step needed? I think the multimod + versions.yaml file are used to figure out the TAG value.
| ssh-add <YOUR_SSH/GPG_KEY_PATH> | ||
| make push-tags | ||
| ``` | ||
| 6. Create a repo level tag and push it: |
There was a problem hiding this comment.
Could you give more context on why we need a repo wide tag?
axw
reviewed
Oct 13, 2025
| is automated and should not be performed manually unless there are specific reasons for this. | ||
|
|
||
| 1. (optional) Determine the version number that will be assigned to the release. It should | ||
| match the latest upstream release version (`OTEL_VERSION`). |
There was a problem hiding this comment.
IIANM we decided to:
- not align to upstream, but instead bump the minor version each time we release
- release after each upstream release, and maybe also in between
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #812
From now on we release all components horizontally on our own pace based on the
make push-tagscommand and usingversions.yamlas the source of truth. (based on #812 (comment))Docs have been updated accordingly.