# New Taquito stable release - v25.1.0

**URL:** https://forum.tezosagora.org/t/new-taquito-stable-release-v25-1-0/7211
**Category:** Project Updates
**Tags:** taquito
**Created:** [October 19, 2026, 5:09pm UTC](https://forum.tezosagora.org/t/new-taquito-stable-release-v25-1-0/7211 "2026-10-19T17:09:14Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![jevonearth](https://forum.tezosagora.org/user_avatar/forum.tezosagora.org/jevonearth/32/144_2.png) [@jevonearth](https://forum.tezosagora.org/u/jevonearth)
#### Post date: [October 19, 2026, 5:19pm UTC](https://forum.tezosagora.org/t/new-taquito-stable-release-v25-1-0/7211/2 "2026-10-19T17:19:01Z")

</div>

One side note on this release:

After our Tezos Foundation grant ended earlier this year, we were assured at length that their `octez.js` fork ([`trilitech/octez.js`](https://github.com/trilitech/octez.js) / `@tezos-x/octez.js`) was only a contingency, and that there would be no changes as long as we continued maintaining Taquito. Later over the summer, they cut us off from the Slack-Connect channels because we no longer had an active TF agreement, and dropped me from the `proto-ecosystem` calls. That part is particularly ironic, since another community member and I started those calls years ago as a grassroots effort to fix coordination problems across the ecosystem.

No one from TF, Trilitech, or Nomadic Labs has reached out to me about `octez.js` since. However, I noticed last week, right after posting `v25.1.0-beta0`, that [`trilitech/octez.js`](https://github.com/trilitech/octez.js) actually has what looks like a full-time effort behind it:

- The Tezos X Previewnet bug reports filed on Taquito ([`#3437`](https://github.com/ecadlabs/taquito/issues/3437), [`#3438`](https://github.com/ecadlabs/taquito/issues/3438), [`#3439`](https://github.com/ecadlabs/taquito/issues/3439)) that I spent my spare time fixing for this release were actually found while testing `@tezos-x/octez.js`, and cross-filed to `trilitech/octez.js` six minutes later ([`#61`](https://github.com/trilitech/octez.js/issues/61), [`#62`](https://github.com/trilitech/octez.js/issues/62), [`#63`](https://github.com/trilitech/octez.js/issues/63)) with the `@tezos-x/octez.js` imports swapped to `@taquito/*` for our issue tracker.
- They are running an automated [`Taquito Sync Tracker` (#53)](https://github.com/trilitech/octez.js/issues/53) monitoring `ecadlabs/taquito` commits and a [`check:rebrand` linter](https://github.com/trilitech/octez.js/blob/master/CLAUDE.md) to scrub `taquito` and `ecadlabs` references.
- Hours after I published `v25.1.0-beta0`, they systematically backported my fixes and `tz5` post-quantum implementation into `octez.js` ([PR #137](https://github.com/trilitech/octez.js/pull/137), [PR #144](https://github.com/trilitech/octez.js/pull/144), [PR #145](https://github.com/trilitech/octez.js/pull/145)).

To be clear, I’m not looking to win back TF funding, and I’ll be glad to wrap up my Taquito maintenance once `octez.js` is officially announced and supported.

Still, saying one thing while doing the opposite (cutting us off from Slack and the coordination calls we helped start, filing `octez.js` bugs on our repo with swapped imports so I fix them in my spare time, and running an automated find-and-replace pipeline to harvest the commits without a word of communication) is a sad demonstration of bad culture, and shows just how low-trust this environment has become.

---

_[View the full topic](https://forum.tezosagora.org/t/new-taquito-stable-release-v25-1-0/7211)._