fix(ci): bump mysticat-ci pin from @v2 to @v3#2865
Merged
Conversation
@v2 is a frozen floating tag — mysticat-ci's main has moved on to v3 (adds an optional, default-off mac-giver-caller input; no breaking changes for consumers that don't set it). Bumping the pin lets this repo pick up adobe/mysticat-ci#22 (decouples it-postgres from build, roughly halving PR CI wall-clock time) once that fix is merged and released, without a further pin change here.
Merged
3 tasks
|
This PR will trigger a patch release when merged. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
aniham
marked this pull request as ready for review
July 21, 2026 11:24
solaris007
approved these changes
Jul 21, 2026
solaris007
pushed a commit
that referenced
this pull request
Jul 22, 2026
## [1.679.1](v1.679.0...v1.679.1) (2026-07-22) ### Bug Fixes * **ci:** bump mysticat-ci pin from [@v2](https://github.com/v2) to [@V3](https://github.com/v3) ([#2865](#2865)) ([59c47dc](59c47dc)), closes [mysticat-ci#22](https://github.com/mysticat-ci/issues/22) [mysticat-ci#22](https://github.com/mysticat-ci/issues/22) [mysticat-ci#22](https://github.com/mysticat-ci/issues/22)
Member
|
🎉 This PR is included in version 1.679.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
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
service-ci.yamlpin in.github/workflows/ci.yamlfrom@v2to@v3.@v2is a frozen floating tag pointing at an oldmysticat-cicommit;mainthere has since moved tov3, which only adds an optional, default-offmac-giver-callerinput — no breaking changes for consumers (like this repo) that don't set it.Why
Opened as a companion to adobe/mysticat-ci#22, which removes the artificial
needs: builddependency on theit-postgresjob (it doesn't consume anythingbuildproduces). Measured on this repo's PR runs:build~6m13s,it-postgres~6m36s, run sequentially today for ~13min total.mysticat-ci#22 has merged and shipped as
v3.1.3, with the floatingv3tag moved to point at it. Re-running this PR's CI confirms the fix:buildandit-postgresnow start within 1 second of each other (previously sequential), and the run completed in ~7min total instead of ~13min.Test plan
@v3withvpc-enabled: true,it-postgres: true,bundle-build: true(nomac-giver-callerset, so behavior should be identical to@v2until mysticat-ci#22 lands).buildandit-postgresstart concurrently on this repo's next PR run and total CI time drops as expected.