--- tags: - release-notes - reference ai: generated title: TerminusDB 11.0 Changelog nextjs: metadata: title: TerminusDB 11.0 Changelog — Release Notes description: 'All TerminusDB 11.0 open-source releases in one place: release notes, bug fixes and new features for every version, newest first, with links to feature pages.' keywords: terminusdb 11.0 changelog, terminusdb 11.0 release notes, terminusdb releases alternates: canonical: https://terminusdb.com/docs/releases/11-0-changelog/ --- Every open-source release in the TerminusDB 11.0 line, newest first. Releases marked with a feature page link have a dedicated write-up of what shipped. ## v11.0.6 {% #v11-0-6 %} Released 3 May 2023 · [GitHub release](https://github.com/terminusdb/terminusdb/releases/tag/v11.0.6) · [Feature page](/docs/releases/11-0-6-automatic-schema-migrations/) TerminusDB Server v11.0.6 Release Notes ### Bug fixes - Unused optional properties would cause GraphQL to fail - Enums were not working properly for collection types in GraphQL - Incorrect version checking on system graphs caused superfluous graph updates on startup - Modifications of classes with `@oneOf` would leave stale objects in the schema graph - Diffing sets now works - Fix error reporting when pushing nonexistent remotes - GraphQL did not work properly with `@oneOf` properties - Memory leak in document API - Crash when processing several compressed requests in the same session ### New - On schema modifications, a migration will be inferred when possible. - New options added to document interface ** `allow_destructive_migration`: Allow for inference of migrations that will also modify instance data. If set, the schema modification will also automatically transform any instance objects already in the database. ** `require_migration`: This will cause the request to fail for schema changes for which no migration can be inferred. ### Enhancement - diff endpoint now has `start` and `count` options for paged results - Improve memory footprint when retrieving lots of documents through the document API - Support JSON objects in GraphQL ## v11.0.5 {% #v11-0-5 %} Released 12 April 2023 · [GitHub release](https://github.com/terminusdb/terminusdb/releases/tag/v11.0.5) ### TerminusDB Server v11.0.5 Release Notes ### Bug fixes - diff endpoint was mishandling subdocuments ## v11.0.4 {% #v11-0-4 %} Released 12 April 2023 · [GitHub release](https://github.com/terminusdb/terminusdb/releases/tag/v11.0.4) · [Feature page](/docs/releases/11-0-4-document-history-api/) ### TerminusDB Server v11.0.4 Release Notes ### New - New history API to find out when an object changed ### Enhancement - Keep loaded layers in an LRU cache for faster repeated queries - Optimize will now also optimize schema layers - Improved memory use during commits and squashes ### Experimental - New endpoint for schema migrations which also transforms existing data - Support updating a schema from a target branch as long as there is a migration ## v11.0.3 {% #v11-0-3 %} Released 16 March 2023 · [GitHub release](https://github.com/terminusdb/terminusdb/releases/tag/v11.0.3) · [Feature page](/docs/releases/11-0-3-patch-endpoint/) ### Bug fixes - Prevent early failure on full schema replace where id is missing - Support stringy filters on all stringy types, not just strings - Return 204 on doc delete (and disable chunking for non-gets) - Fix inversion naming issue. This causes issues when using non-standard GraphQL class names ### New - Adding Patch Endpoint for Resources - Implement pinned organization ENV variable to keep data products of whole organizations/teams in memory ## v11.0.2 {% #v11-0-2 %} Released 6 March 2023 · [GitHub release](https://github.com/terminusdb/terminusdb/releases/tag/v11.0.2) ### TerminusDB Server v11.0.2 Release Notes ### Bug fixes - On replace, schema documentation entities were not cleaned up properly - Fix support for ne (not equal) operator in graphql ## v11.0.1 {% #v11-0-1 %} Released 22 February 2023 · [GitHub release](https://github.com/terminusdb/terminusdb/releases/tag/v11.0.1) · [Feature page](/docs/releases/11-0-1-local-clone-pre-commit-hooks/) ### TerminusDB Server v11.0.1 Release Notes ### Backwards-incompatible changes - Document replacement allowed insertion of nested documents, even without the create option specified. We decided that this was a bug, and made it so that this now errors, unless the create option is specified. This is backwards-incompatible, but we believe that this is the correct behavior. If your code relies on nested documents being inserted, make sure you specify the create option. Note that this is just about nested documents which are top-level types. Subdocuments are not affected. ### New - Introduced support for a grpc label store as an alternative to file-based label lookup [terminusdb-labs/terminusdb-grpc-labelstore](https://github.com/terminusdb-labs/terminusdb-grpc-labelstore) - Implemented local clone - Implement user impersionation in the CLI tool - Added a pre-commit hook to allow implementation of custom schema validations ### Enhancements - Pinned system schema graph so it is only loaded once - Reduced amount of hash roundtrips for newly generated passwords to speed up login - Disabled authentication on the ok endpoint for faster roundtrip - Removed default SWI-Prolog HTTP server welcome message - Improved db list speed ### Bug fixes - Fixed startup message when no store is present - Ensured that all users automatically have all capabilities of anonymous - Delete the stale database if a clone fails - Fix SSL issues in fetch and push: newer version of openssl errors when a connection is closed unexpectedly - Fix accidental insertion of duplicate nested documents - Fixed GYear support ## v11.0.0 {% #v11-0-0 %} Released 30 January 2023 · [GitHub release](https://github.com/terminusdb/terminusdb/releases/tag/v11.0.0) · [Feature page](/docs/releases/11-0-0-typed-storage-backend-migration/) ### TerminusDB Server v11.0.0 Release Notes ### Backwards-Incompatible Changes - This release changes the storage format of TerminusDB. After installing this version, you will also need to upgrade your storage directory, or the server will not start. A conversion tool is provided at [terminusdb-10-to-11](https://github.com/terminusdb/terminusdb-10-to-11). This is also bundled with [terminusdb-bootstrap](https://github.com/terminusdb/terminusdb-bootstrap). - TerminusDB 11 now responds to `xsd:integer`, `xsd:decimal`, and all of the unbounded sub-types of these two objects in the document interface with strings. This is because many (even most) JSON libraries can not handle arbitrary precision integers, and (few if any) can handle arbitrary precision floats. It should still be possible to submit documents using integers or floats, but when returned they will be strings. ### Enhancements - New Storage backend - Added typed storage for a wide variety of XSD types, reducing storage overhead and improving search performance - Introduce a layer archive format reducing storage use and latency and simplifying interchange. - GraphQL `_type` added to objects to return the exact rather than subsumed type - Added `@unfoldable` document flag to frames - Add `@metadata` to frames ### Bug fixes - Fixed a bug in inverse fields in GraphQL - Removed extraneous system objects from GraphQL schema - Improved completeness of GraphQL schema handling - Added x-method-override header to CORS - Fixed GraphQL naming bug leading to GraphQL schema crashes