Summary
Quebec Protocol Support
New Features
@taquito/rpc - Added getSpendable, getBalanceAndFrozenBonds and getSpendableAndFrozenBonds rpc endpoint #3023
Improvement
@taquito/rpc - Updated getPendingOperations with param source and operationHash #3034
@taquito/rpc - Added Quebec protocol constant, ConstantsResponseProto021, to ConstantsResponse #3037
@taquito/rpc - Removed endorsement compatibility (still kept rpc types and readProvider for user querying old blocks) #3036
Documentation
Updated documentation with Quebec support #3068
Fixed maps_bigmaps live code example bugs #3068
Internals
Updated dependencies #3068
Updated Taquito test dapp with Quebec support #3068
FAQ: “Why do I need to upgrade to the latest version of Taquito (v21) for the Quebec protocol if there are no breaking changes?”
While it’s technically possible to continue using a prior version of Taquito, we strongly recommend upgrading to the latest major release. Here’s why:
-
Thorough Testing & Official Support
The latest major version (v21) is the one we ensure is tested and verified against the new Tezos protocol (Quebec). Even if there are no breaking changes, running an older version means less certainty that it will remain fully compatible and supported as the protocol continues to evolve. -
Continuous Improvements
Each Taquito release includes more than just protocol-specific updates. By upgrading, you benefit from bug fixes, performance enhancements, and new features—these aren’t generally back-ported to older versions. For instance, the Beacon library has undergone several improvements in recent minor and patch releases, so using the latest Taquito will give your dApp the best possible experience for your users. -
Reduced Upgrade Friction
Staying on current releases helps you avoid compounding changes and potential refactors. By updating regularly, you’ll experience less friction when a future version does introduce a breaking change or a big feature release. -
Future Readiness
Taquito’s versioning strategy follows the Tezos protocol. Major versions track the latest protocol, ensuring that dApps and wallets built with Taquito are prepared for upcoming amendments or new functionalities the protocol may introduce. -
Community & Ecosystem Alignment
As the Tezos ecosystem moves forward, libraries, tooling, and documentation converge around the latest release. Aligning your project with v21 helps you stay connected to active resources, community support, and best practices.
Although we do our best to maintain backward compatibility as far as feasible, it’s best practice to keep your dependencies current. This approach gives you the smoothest experience, the most robust test coverage, and optimal support from the Taquito team.