Update release test CI to use default pinned versions#109
Merged
Conversation
Cherry-pick CI changes from main onto the release branch: - release-test.yml: add bazel-cache action, permissions, concurrency group, rename job to "Bootstrap with default pinned versions" - release_test.sh: remove --valdiVersion=main / --valdiWidgetsVersion=main overrides so the test uses the CLI's default pinned tags - Add .github/actions/bazel-cache/action.yml (new dependency) The old workflow bootstrapped from main (bleeding edge) which broke when main's resvg_libs strip_prefix diverged from the archive structure.
📊 PR Size: size/MTotal changes: 144 lines (3 files) Top files changed:
Size calculated as additions + deletions. Labels: XS (<10), S (<50), M (<250), L (<1000), XL (1000+) |
The release branch was cut from beta-0.1.0 which still had beta-0.0.3 as the default tags. The release test now uses pinned defaults, so these must point to a version with MODULE.bazel support (beta-0.0.3 predates bzlmod).
|
| Test Suite | Result |
|---|---|
| Snapshot Tests | ❌ cancelled |
| Valdi Smoke Tests | ❌ cancelled |
| Linux: C++ Tests | ❌ cancelled |
| Linux: Build & Export | ❌ cancelled |
| Comment Test Results / Post Results Comment | ❌ null |
Some tests failed. Please check the workflow logs for details.
🚀 Bazel disk cache is enabled - builds with warm cache will be faster!
Workflow: Valdi CI
|
| Test Suite | Result |
|---|---|
| Linux: Build & Export | ✅ success |
| Valdi Smoke Tests | ❌ failure |
| Linux: C++ Tests | ✅ success |
| Snapshot Tests | ✅ success |
| Comment Test Results / Post Results Comment | ❌ null |
Some tests failed. Please check the workflow logs for details.
🚀 Bazel disk cache is enabled - builds with warm cache will be faster!
Workflow: Valdi CI
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Summary
Update the release test workflow on the
release/beta-0.1branch to match main's current CI configuration. The old workflow bootstrapped from main (bleeding edge), which broke when main'sresvg_libsstrip_prefixdiverged from the archive structure.Changes
.github/workflows/release-test.yml: Add bazel-cache action, permissions, concurrency group; rename job to "Bootstrap with default pinned versions"tools/ci/release_test.sh: Remove--valdiVersion=main/--valdiWidgetsVersion=mainoverrides so the test uses the CLI's default pinned tags (beta-0.1.0).github/actions/bazel-cache/action.yml: New composite action (dependency of the updated workflow)Cherry-picked from
ed075b75d959— Add bazel-cache action, permissions, concurrency groupdeeee13100e6— Workflow trigger updatesd75e5dfed2fb— Switch from bleeding-edge to default pinned versionsa0d12c397acc— bzlmod verification + MODULE.bazel artifact uploadContext
The release test for
beta-0.1.1failed because the old workflow tested against main's bleeding edge, which has a brokenresvg_libsarchive prefix. Switching to pinned versions makes the release test validate the actual user experience.