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

Improve BCR release process #301

Merged
merged 4 commits into from
Jan 31, 2025
Merged

Conversation

jchadwick-buf
Copy link
Member

  • New workflow to create release tag (Yes I know, but it seemed trivial enough to add.)
  • New workflow to create draft release
  • BCR release prep script, adds Bazel snippets to release notes like other Bazel projects, creates stable release tarball

This should take care of the issues we have with the BCR publishing process, I think.

- New workflow to create release tag (Yes I know, but it seemed trivial enough to add.)
- New workflow to create draft release
- BCR release prep script, adds Bazel snippets to release notes like other Bazel projects, creates stable release tarball
Copy link

github-actions bot commented Jan 31, 2025

The latest Buf updates on your PR. Results from workflow Buf CI / buf (pull_request).

BuildFormatLintBreakingUpdated (UTC)
✅ passed✅ passed✅ passed✅ passedJan 31, 2025, 4:03 PM

Copy link
Member

@nicksnyder nicksnyder left a comment

Choose a reason for hiding this comment

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

Can you add a RELEASING.md or equivalent to document the steps to take to do a release. e.g.

1. Go here (link) to start this workflow and wait for it to complete.
2. Go to https://github.com/bufbuild/protovalidate/releases to find the draft release that was just created.
4. Edit release notes if necessary.
5. Publish the release.
6. Check to see that a PR was created on [bazel-central-registry](https://github.com/bazelbuild/bazel-central-registry/pulls?q=is%3Apr+is%3Aopen+protovalidate)

.github/workflows/create-release-draft.yaml Show resolved Hide resolved
ARCHIVE="${PREFIX}.tar.gz"

# Update MODULE.bazel version
>&2 echo "# Update MODULE.bazel version to ${TAG:1}"
Copy link
Member

Choose a reason for hiding this comment

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

why are we redirecting all output to stderr?

Copy link
Member Author

Choose a reason for hiding this comment

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

Not any specific reason, I just tend to use stderr for logging and stdout for results, so I tend to do this without really thinking much.

@jchadwick-buf
Copy link
Member Author

jchadwick-buf commented Jan 31, 2025

Added a RELEASING.md file.

@jchadwick-buf jchadwick-buf merged commit 0390a45 into main Jan 31, 2025
6 checks passed
@jchadwick-buf jchadwick-buf deleted the jchadwick/bcr-release-improvements branch January 31, 2025 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants