Explore · Breaking
Breaking Changes per Major Version
Verified breaking changes between major versions, with migration hints. Call this before any major-version bump.
Recent breaking changes (12)
| Package | From → To | Type | Breaking change | Migration hint |
|---|---|---|---|---|
| nuget/Azure.Messaging.ServiceBus | unknown→Azure.Storage.Blobs_12.30.0-beta.1 | breaking | Block IDs generated during partitioned uploads are now randomly generated instead of based on sequential integers. This ensures uniqueness across concurrent uploads to the same blob but means block IDs are no longer predictable or ordered. | — |
| nuget/Azure.Security.KeyVault.Secrets | unknown→Azure.Storage.Blobs_12.30.0-beta.1 | breaking | Block IDs generated during partitioned uploads are now randomly generated instead of based on sequential integers. This ensures uniqueness across concurrent uploads to the same blob but means block IDs are no longer predictable or ordered. | — |
| nuget/Azure.Storage.Blobs | unknown→Azure.Storage.Blobs_12.30.0-beta.1 | breaking | Block IDs generated during partitioned uploads are now randomly generated instead of based on sequential integers. This ensures uniqueness across concurrent uploads to the same blob but means block IDs are no longer predictable or ordered. | — |
| nuget/Azure.Storage.Common | unknown→Azure.Storage.Blobs_12.30.0-beta.1 | breaking | Block IDs generated during partitioned uploads are now randomly generated instead of based on sequential integers. This ensures uniqueness across concurrent uploads to the same blob but means block IDs are no longer predictable or ordered. | — |
| nuget/System.ClientModel | unknown→Azure.Storage.Blobs_12.30.0-beta.1 | breaking | Block IDs generated during partitioned uploads are now randomly generated instead of based on sequential integers. This ensures uniqueness across concurrent uploads to the same blob but means block IDs are no longer predictable or ordered. | — |
| nuget/Azure.Identity | unknown→Azure.Storage.Blobs_12.30.0-beta.1 | breaking | Block IDs generated during partitioned uploads are now randomly generated instead of based on sequential integers. This ensures uniqueness across concurrent uploads to the same blob but means block IDs are no longer predictable or ordered. | — |
| nuget/Azure.Core | unknown→Azure.Storage.Blobs_12.30.0-beta.1 | breaking | Block IDs generated during partitioned uploads are now randomly generated instead of based on sequential integers. This ensures uniqueness across concurrent uploads to the same blob but means block IDs are no longer predictable or ordered. | — |
| julia/TensorNetworkQuantumSimulator | v0.1.4→v0.2.0 | breaking | Refactor (#42) (@JoeyT1994) | — |
| julia/TensorNetworkQuantumSimulator | v0.2.13→v0.3.0 | breaking | Fix gate defs (#59) (@JoeyT1994) | — |
| julia/TensorNetworkQuantumSimulator | v0.2.13→v0.3.0 | breaking | Re-defined the `Rxxyyzz` and `Rxxyy` gate due to the previous definition being incorrect. | — |
| julia/TensorNetworkQuantumSimulator | v0.3.11→v0.4.0 | breaking | the automatic PTM gate-application path for Pauli-tagged site indices Heisenberg-picture / operator tensor networks are now built with a doubled ket/bra representation instead: two physical indices per site (`siteinds(sitetype, g; inds_per_site = 2)`), with `identity_tensornetworkstate` giving the identity operator and gates applied as a pair of ops (one on the ket leg, one on the bra leg) per site. See `examples/2dIsing_dynamics_Heisenbergpicture.jl` for the updated pattern. | — |
| julia/TensorNetworkQuantumSimulator | v0.3.11→v0.4.0 | breaking | `"Pauli"` as a valid `sitetype` string (`siteinds`, `site_dimension`, `site_tag`) | — |
Sample of curated entries across ecosystems. Search for a specific package above.
What we track
Curated major-version transitions for packages that matter to AI coding agents: React, Next.js, Prisma, Express, Node, TypeScript, ESLint, Tailwind, Vite, Pydantic, SQLAlchemy, Django, Python, Rust editions, Rails, Laravel, Symfony, Spring Boot, Jakarta EE, .NET, Swift and more. Each entry links the breaking behaviour with a tested migration command or code pattern.