The team updated today the internal integration environment to 0.14.1. Testnet, and then Mainnet, are expected in a few weeks. 0.14.1 is a medium-size step for Starknet, but today I focus on it representing a big mind-shift in Starknet development. We had big breaking changes in the past, forcing apps to work hard to stay in place. But as Starknet matures, and aims to be the best place to build on, this can't continue. 0.14.1 represents this, and here is why With the release of S-Two, some hashes that were chosen to fit Stone became relatively expensive. These hashes are used everywhere, from hashing calldata to reads and writes. 0.14.1 didn't say, "let's change all hashes we can to be the cheapest out there and force everyone to adapt". It says: lets migrate, carefully, only the places builders won't feel and are mostly under the hood. Lets then coordinate with SDKs to ensure developers really aren't feeling a thing (as long as they update their SDK somewhat regularly). Hell, lets prepare in advance list of transactions aimed only to migrate these hashes, as part of the upgrade process, to ensure that any tx that was valid before will be still valid, without anyone needing to lift a finger I can't guarantee that there will never be another breaking change in Starknet. But I can guarantee that this mindset is here to stay.