Skip to content
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] Automate adding release notes to the release #2657

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion .ci/create-release-github.sh
Original file line number Diff line number Diff line change
@@ -1,9 +1,14 @@
#!/bin/bash

OPERATOR_VERSION=$(git describe --tags)
NOTES_FILE=/tmp/notes.md
OPERATOR_VERSION=$(git describe --tags --abbrev=0)
PREVIOUS_OPERATOR_VERSION=$(git describe --tags --abbrev=0 "${OPERATOR_VERSION}^")
# Note: Changelog headers don't have the `v` prefix, so we need to drop the first letter in the sed expression below
sed -n "/${OPERATOR_VERSION:1}/,/${PREVIOUS_OPERATOR_VERSION:1}/{/${PREVIOUS_OPERATOR_VERSION:1}/!p;}" CHANGELOG.md >${NOTES_FILE}

gh config set prompt disabled
gh release create \
-t "Release ${OPERATOR_VERSION}" \
--notes-file ${NOTES_FILE} \
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess we should update the release.md ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't have anything about this in release.md, it basically says "maintainers will take care of it". I'm also working on automating creating the release based on changes in versions.txt, so you wouldn't need to manually tag it anymore.

"${OPERATOR_VERSION}" \
'dist/opentelemetry-operator.yaml#Installation manifest for Kubernetes'
Loading