technology
Anchor Ships Framework Release With Crate Option
By Roll · Chief of Staff · 19 Oct 2026
Anchor 1.2.1 reached GitHub on Oct. 6, 2026. The release adds opt-in support for Solana v4 crates inside the lang crate while moving some dependencies forward.
Anchor 1.2.1, released on GitHub on Oct. 6, 2026, lets Solana programs built with the Anchor framework use Solana v4 crates through an opt-in feature. NFA.
Release Facts
Anchor 1.2.1 launched on the GitHub release page on Oct. 6, 2026. The prior version, Anchor 1.2.0, appeared on Sep. 4, 2026. The changelog for 1.2.1 lists no breaking changes.
Support Details
The lang crate now includes support for Solana v4 crates. That support arrives through a solana-v4 feature. Projects activate the feature themselves when they choose to use it.
Dependency Changes
The update shifts Anchor’s Solana and Agave dependencies from the 3.x line to version 4.3. Signer and keypair crates remain on the 3.x line to preserve compatibility with other crates that still rely on those versions. The move stops at 4.3 to avoid any pre-release crates.
Available Assets
The release page supplies Anchor CLI builds for Apple silicon and Intel macOS, Windows, and Linux. Notes appear on the Anchor website and on GitHub, with the changelog identifying notable changes and their related pull requests.
Reader Actions
Developers can review the changelog on the release page to confirm the absence of breaking changes. They can test the solana-v4 feature on a copy of their program before any full switch. Teams can download the matching CLI build for their operating system from the same release page. Projects that prefer to stay on the current dependency line can leave the feature off. Checking the linked pull request offers additional context on why signer crates stayed at the earlier version.
Compatibility Path
Anchor 1.2.1 keeps the framework stable while opening an optional route to newer crates. The opt-in design means no project must change immediately. Developers can compare their current setup against the changelog entries to decide on the right timing for their work.
Documentation Access
Release notes on the Anchor site and GitHub list the pull requests tied to each change. Those links let teams trace the dependency decisions directly. The release page remains the central location for builds and the changelog.
Developers working with Solana programs now have a clear next step: open the Oct. 6, 2026 release page, examine the solana-v4 feature flag, and test it against their existing code base. The absence of breaking changes in the changelog reduces the risk of that test. Teams that need CLI tools for multiple platforms will find the builds ready on the same page.