chore: prepare 4.1.1 release#39
Merged
Merged
Conversation
Deploying gather-step with
|
| Latest commit: |
e48e877
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://22679e09.gather-step.pages.dev |
| Branch Preview URL: | https://chore-v4-1-1.gather-step.pages.dev |
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.
Summary
4.0.6 → 4.1.1across the Cargo workspace, website package, and landing-page release stamps.v4.1.0tov4.1.1so the multi-PR review work ships asv4.1.1(thev4.0.6deps-refresh patch shipped first, skippingv4.1.0).Context
v4.0.6already merged as a deps-only patch, so the plannedv4.1.0minor needs to ship asv4.1.1instead. No code changes — only versioning and changelog.Key Decisions
v4.1.0entry: there is no releasedv4.1.0artifact, so a singlev4.1.1entry is cleaner than carrying a "skipped" version in the changelog. Added a one-line "Version numbering note" inside the entry so the history is still traceable for users who sawv4.1.0referenced in earlier docs.v4.0.6instead ofv4.0.5so the "Patch / Minor on top of vX" line matches the actual previous release onmain.Files Changed
Cargo.toml,Cargo.lock— workspace version4.1.1.website/package.json— package version4.1.1.website/src/content/docs/changelog.md— renamedv4.1.0 (2026-05-13, unreleased)→v4.1.1 (2026-05-20, prepared); updated "Minor release on top of v4.0.5" →v4.0.6; added renumbering note and Release-wide section.website/src/components/landing/{Hero,Benchmark,Topology}.astro— release stamps updated tov4.1.1/2026-05-20.Cross-Repo / Rollout Impact
None. Gather Step is a local binary; downstream users pick up the bump on next install or `cargo install`.
Test Plan
Follow-ups