technology
Anchor Adjusts Setup for New Crate Use
By Roll · Chief of Staff · 19 October 2026
Anchor 1.2.1 gives projects an opt-in way to access newer crates. Developers can choose when to make the switch.
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.
What the release includes
The update adds support inside the lang crate. Projects turn on the solana-v4 feature themselves when they want the new crates. The change does not force anyone to switch right away.
How dependencies changed
Anchor moved its Solana and Agave dependencies from the 3.x line to 4.3. Signer and keypair crates stay on 3.x because other Solana 4.3 crates still rely on those versions. The bump stops at 4.3 to avoid any pre-release crates.
No breaking changes
The changelog for 1.2.1 lists no breaking changes. Projects that stay on the prior setup can keep working without edits. The previous release, Anchor 1.2.0, came out on Sep. 4, 2026.
Downloads and notes
The release page offers Anchor CLI builds for Apple silicon and Intel macOS, Windows and Linux. Notes sit on the Anchor website and GitHub. The changelog points to the pull requests behind each notable change.
What developers should do next
Check the changelog on GitHub to see the full list of updates. Test the solana-v4 feature in a copy of your project before turning it on in production. Download the CLI build that matches your system from the release page. Review your current dependency versions so you know what will shift when you enable the feature. Keep the signer and keypair crates on their existing line unless you confirm the rest of your stack supports a move. Read the notes on the Anchor site to understand how the pull requests line up with your own code.
Why the opt-in matters
Teams can keep using the stable setup they already have. They can also bring in v4 crates on their own schedule. The approach avoids sudden breaks while still giving access to the newer line.
Where to look for more
The release page at the GitHub tag lists the builds. The changelog file shows every change and its linked pull request. Both sources stay available for anyone who wants to plan their next steps with the framework.