chore: release v0.6.27 — ship pipeline auto-commit - #560
Merged
Conversation
githubrobbi
enabled auto-merge
July 14, 2026 14:17
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Jul 14, 2026
deep-soft
pushed a commit
to deep-soft/UltraFastFileSearch-Rust
that referenced
this pull request
Jul 16, 2026
) ensure_warm_for_dispatch_promotes_in_parallel asserted both loader.peak() >= 2 (deterministic: concurrent loads observed) and elapsed < 1.5x delay (a wall-clock proxy). The wall-clock bound flaked on cold/contended CI runners (notably Windows, where the nightly-2026-07-14 cache miss plus blocking-pool ramp-up pushed even a correct parallel run past 150ms), which ejected release PR skyllc-ai#560 from the merge queue. The peak-in-flight counter already proves the parallelism contract with no timing race: a serial re-promote loop never exceeds peak 1. Drop the redundant wall-clock assertion and rely on the deterministic signal.
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
just shipPhase 2 auto-commit for v0.6.27 — the[workspace.package].versionbump inCargo.toml. This PR routes that commit through branch-protection rules. Once it merges tomain, runjust release-tagto cut the signedv0.6.27tag, which firesrelease.ymland builds the cross-platform binaries + GitHub Release v0.6.27. (No auto-tag on merge — the tag step is manual on-demand, Path B.)Auto-merge
--auto --squashis queued — GitHub will merge as soon as the required status checks pass. Squash is required becausemain-protectionmandates signed commits, and GitHub's rebase-auto-merge cannot sign the rebased commit; the squash-merge commit is signed by GitHub's own key, which satisfiesrequired_signatures: true. The original author's signed commit remains verifiable in the PR branch history.After merge
The auto-commit lived only on
release/v0.6.27, so localmainnever drifted — sync it with a plaingit pull --ff-only origin main(noreset --hardneeded).