-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
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
[chore] Prepare release 0.118.0 #37386
Conversation
side note: the merge freeze workflow is working fine for PRs that are up-to-date with mainline https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/12893441428/job/35950354844?pr=37384 However, for PRs that are approved but not up to date, they can still be merged. Guess this can be fixed once merge queue is enabled in this repo. |
@songy23 Yes, that's the expected behavior. AFAIK, the only way to have updated merge freeze status on PRs would be to go through every open PR and rerun the check, which is a bit complex to automate, so (at least for now) we've decided to rely on the merge queue for proper enforcement. Thank you for checking by the way! (I had planned to do it myself with a draft PR but forgot that it would happen in the evening here.) |
The following commands were run to prepare this release: - make chlog-update VERSION=v0.118.0 - sed -i.bak s/0[.]117[.]0/0.118.0/g versions.yaml - make multimod-prerelease - make multimod-sync
The following commands were run to prepare this release: