Repository navigation
ci: add Turso Pin Watch — daily bump PR when crates.io is ahead - #41
Merged
Merged
Conversation
|
ePHPm Preview — removed Preview deployment has been torn down. |
|
ePHPm Preview — deployed (health check pending)
Preview updates automatically on each push to this PR. |
This branch was successfully deployed
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
1 participant
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.
Adds a daily poll (+
workflow_dispatch) that opens abump/turso-<ver>PR when crates.io publishes a newer stabletursothan the exact pin in the workspaceCargo.toml. Auto-PR only — merge is manual.litewire owns the turso version for the whole ePHPm stack — ePHPm pins the same
turso = "=X.Y.Z"only so it resolves to litewire's one turso instance, and ePHPm can't bump until litewire has. So this watcher is the origin of a turso bump: once its PR merges,ephpm/ephpm'sturso-pin-watchdetects litewire is ahead and opens the matching (litewire rev + turso pin) PR there automatically.Review is never skipped — turso is Beta upstream and CDC / vtab-TVF / PRAGMA behavior moves between releases, so each PR carries the
cargo updatedelta and a checklist (changelog review of those surfaces + updating the hand-written pin-rationale comment).Modeled on
ephpm/ephpm'swatch-vivacity.yml(marker-branch idempotency; the^turso =pin parse deliberately ignores thelitewire-tursopath crate). Token caveat documented in-file: default-GITHUB_TOKENPRs don't trigger CI — close/reopen to get a run.Nothing to bump today (crates.io
tursolatest =0.7.2= current pin); this is the mechanism. I canworkflow_dispatchit after merge as a no-op smoke test.