Repository navigation
Conversation
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
|
gregjkal
force-pushed
the
release/0.3.1
branch
from
November 20, 2026 13:18
1373744 to
5578ffb
Compare
355495beed7f4777
This branch has not been 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
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.
Prepares the 0.3.1 installer release. The workspace version goes from 0.3.0 to 0.3.1, and the Workshop pin moves from
623eb7aatoed7f4777, the 0.3.1 bump in cppalliance/runvil-workshop#28 on top of Workshopmaster68c72495. Av0.3.1tag can then publish, sincev0.3.0is already taken by the old pipeline.cargo installerrefuses a Workshop checkout whose version differs from this workspace's, so the two bumps go together.Landing, in order:
ed7f4777stays the commit on Workshopmasterthat this pin names.installers.ymlrun onmaster. Pull-request mode runs only theallandworkshopcells; the full run adds thegatewaycells and the Windowsgateway-sttandrejectionscells, so a failure there costs nothing instead of a tag.v0.3.1on themastercommit.Because
Cargo.tomlchanges, this PR runsinstallers.ymlin pull-request mode against the pinned Workshop.Known, not changed here: the
workshop-latesttag already exists ate6fa867awith no release, so the first release'sgh release create workshop-latestattaches the evergreen release to that old commit. Its download URLs still work.Local:
cargo test -p build-xtask -p build-installerpasses, withRUNVIL_WORKSHOPnaming a checkout ofed7f4777.