Skip to content

Conversation

jacky8hyf
Copy link
Collaborator

@jacky8hyf jacky8hyf commented Jul 16, 2025

@jacky8hyf jacky8hyf requested a review from Gansito144 July 16, 2025 18:50
@jacky8hyf jacky8hyf changed the title fix(github-actions): update reference to release.yaml in tag.yaml Fix release process Jul 16, 2025
@jacky8hyf jacky8hyf force-pushed the release branch 4 times, most recently from b9684af to 258578b Compare July 16, 2025 22:04
@jacky8hyf jacky8hyf changed the title Fix release process fix(github-actions): Fix release process Jul 16, 2025
@jacky8hyf jacky8hyf force-pushed the release branch 4 times, most recently from f8ae4c4 to 1769115 Compare July 16, 2025 22:41
tharakadesilva and others added 4 commits July 17, 2025 19:58
In release.yaml, ensure that ci.yaml has passed before cutting a
release. This adds e2e tests to the release.

Because CI are added, there is no need to run bazel test separately
any more.

addresses bazel-contrib#5
We don't support Bazel 6 due to the use of use_repo_rule; it is
also not part of the CI. Mention that in the release notes.

addresses bazel-contrib#5
Though the link is not available now, it will be available once
we release.

addresses bazel-contrib#5
@jacky8hyf jacky8hyf marked this pull request as draft July 17, 2025 20:05
Let us make sure the whole process works before re-enabling
auto-publishing to BCR after a release.
@jacky8hyf jacky8hyf marked this pull request as ready for review July 17, 2025 20:20
@jacky8hyf jacky8hyf merged commit 732a5cc into bazel-contrib:main Jul 17, 2025
11 checks passed
@jacky8hyf jacky8hyf deleted the release branch July 17, 2025 20:20
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.

3 participants