Remove updating CHANGELOG step in release workflow #4273
Merged
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
lzchen
added a commit
to open-telemetry/opentelemetry-python-contrib
that referenced
this pull request
Nov 13, 2024
xrmx
approved these changes
Nov 14, 2024
emdneto
approved these changes
Nov 14, 2024
aabmass
pushed a commit
to aabmass/opentelemetry-python
that referenced
this pull request
Nov 14, 2024
This was referenced Nov 14, 2024
aabmass
pushed a commit
to aabmass/opentelemetry-python
that referenced
this pull request
Nov 14, 2024
aabmass
added a commit
that referenced
this pull request
Nov 15, 2024
Co-authored-by: Leighton Chen <[email protected]> Clean cherry-pick of #4273 to the release/v1.28.x-0.49bx branch. Part of #4281
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.
It seems like the prepare-release-branch.yml workflow already sets the release date as the current date in a pr, and we also maintain a list of our most current changes at the top, so we most likely do not need the update CHANGELOG step in main post release.yml workflow.