Anchor 1.2.1 launched on GitHub on Oct. 6, 2026 and adds opt-in support for Solana v4 crates in the lang crate.
Release Overview
The Anchor 1.2.1 release of the Solana program framework arrived on GitHub on Oct. 6, 2026 according to the release page. This update follows the prior Anchor 1.2.0 release that appeared on Sep. 4, 2026 as noted in the changelog. The release page lists Anchor CLI builds for Apple silicon and Intel macOS along with Windows and Linux platforms. Notes for the release sit on the Anchor website and on GitHub with the changelog identifying the notable changes and their pull requests.
Opt In Feature Details
The changelog shows that the lang crate now adds support for Solana v4 crates. This support arrives through a solana-v4 feature so that projects activate the option themselves. Projects do not face a required switch because the feature remains opt in per the changelog. Developers can choose when and whether to enable the solana-v4 feature in their own work.
Dependency Adjustments
The linked pull request describes a move of Anchor Solana and Agave dependencies from the 3.x line to the 4.3 line. The signer and keypair crates remain on the 3.x line because other Solana 4.3 crates continue to rely on those versions. The bump stops at 4.3 to keep Anchor from depending on pre release crates as stated in the pull request. These adjustments affect how programs interact with the updated dependency line while preserving stability in signer components.
Absence Of Breaking Changes
The 1.2.1 changelog records no breaking changes. Programs built with the Anchor framework can review the listed changes and their pull requests without encountering forced modifications to existing code. The release page and changelog together supply the complete set of details for developers to assess the update.
What Developers Receive
Holders of projects that use the Anchor framework receive an opt in path to Solana v4 crate support in the lang crate. The update supplies CLI builds across major platforms so teams can install and test the release directly. Notes hosted on the Anchor website and GitHub give further context on the changes and their associated pull requests. This structure lets developers decide on their own timeline whether to activate the solana-v4 feature after reviewing the dependency shifts.
The changelog and release page form the primary references for the Anchor 1.2.1 release. Developers working with Solana programs gain a defined route to incorporate the new crate support while the signer crates stay unchanged. The overall package keeps the framework compatible with prior setups unless the opt in feature is selected.