Skip to content

chore: release v0.6.27 — ship pipeline auto-commit - #560

Merged
githubrobbi merged 1 commit into
mainfrom
release/v0.6.27
Jul 14, 2026
Merged

chore: release v0.6.27 — ship pipeline auto-commit#560
githubrobbi merged 1 commit into
mainfrom
release/v0.6.27

Conversation

@githubrobbi

Copy link
Copy Markdown
Collaborator

Summary

just ship Phase 2 auto-commit for v0.6.27 — the [workspace.package].version bump in Cargo.toml. This PR routes that commit through branch-protection rules. Once it merges to main, run just release-tag to cut the signed v0.6.27 tag, which fires release.yml and 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 --squash is queued — GitHub will merge as soon as the required status checks pass. Squash is required because main-protection mandates 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 satisfies required_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 local main never drifted — sync it with a plain git pull --ff-only origin main (no reset --hard needed).

@githubrobbi
githubrobbi enabled auto-merge July 14, 2026 14:17
@githubrobbi
githubrobbi added this pull request to the merge queue Jul 14, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Jul 14, 2026
@githubrobbi
githubrobbi added this pull request to the merge queue Jul 14, 2026
Merged via the queue into main with commit 0412432 Jul 14, 2026
22 checks passed
@githubrobbi
githubrobbi deleted the release/v0.6.27 branch July 14, 2026 17:30
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant