Two releases shipped in Q3 2024: 7.14.0 and 7.15.0. They add article and image generation with OpenAI and Dall-E, ARM Docker images, custom OIDC servers for teams, new content update statements and control over field enrichment, plus an update of the management UI to Angular 18.
Two releases went out in the third quarter of 2024, 7.14.0 and 7.15.0. The bigger themes are the AI tools in the management UI, the build and identity setup for self hosted installations, and finer control over how content is written and returned.
The AI tools in 7.14.0 got the largest addition of the quarter. You can generate an article that already contains embedded images, using OpenAI for the text and Dall-E for the images, and you can generate a single image with Dall-E on its own.
Two changes make the tools usable rather than just present. Responses are streamed, so long generations show text as it arrives instead of blocking until the whole answer is finished. And the AI chat now shows which tools were used for a response, so you can see whether an answer came from a plain completion or from an image generation step.
Squidex now builds ARM Docker images. If you run on ARM hardware, you no longer need emulation or your own build.
Two related changes help existing installations. The asset file hash is optional in MongoDB now, which makes newer versions compatible with data written by older installations. And content sharding uses deterministic hash codes, with a separate fix for very long content IDs, so items land on a stable shard.
Identity handling was extended in 7.14.0. You can configure custom OIDC servers for teams, so a team can authenticate against its own identity provider instead of the one configured globally.
The OIDC integration also supports the prompt parameter, which lets you control whether the identity provider re-authenticates the user, asks for consent, or stays silent.
On the write side, 7.14.0 added new update statements for Upsert, Update and Patch. On the read side, 7.15.0 added two flags that control enrichment. One header flag tells Squidex not to enrich queried content items with default values, so you get back what is actually stored. Another flag enriches required fields as well.
The enrichment flags are useful when you synchronize content into another system and need to distinguish between a value that was set and a default that Squidex filled in.
GET /api/content/my-app/articles HTTP/1.1
X-NoEnrichment: true
Authorization: Bearer <token>
Two query fixes belong here too: content queries never return null statuses anymore, and fields that have the same name as a meta field are delivered correctly instead of being shadowed.
GraphQL uses a proper JSON type now, which means mutations that pass JSON through variables work as expected. The sourceUrl field on assets is nullable in the GraphQL schema, matching the fact that not every asset has one. Some types in the generated OpenAPI document were corrected.
The management UI was updated to Angular 18 and migrated to the Angular control flow syntax. Beyond the framework update, the release notes list a long series of smaller corrections.
In the content area, you can open a content item in a new tab from a menu item in the content list, cursors are positioned correctly in the content view, and the inline editor in the content list received several fixes. Reference fields use the correct name. Workflows use the correct version, normal or draft, when they evaluate a content item.
The filter UI supports the NOT operator, the IN operator translates better, filter rows are removed correctly when the delete button is used, and the query dialog shows filters when you select references.
In the rich text editor, clipboard behavior was fixed and the code editor is editable in markdown mode. Autocompletion in the code editors works again.
Navigation keeps the browser history intact, and the back button on the content page navigates to the correct page.
Editor extensions receive a new event when the context has been changed, so a custom editor can react instead of reading state once at startup. The embed SDK supports data attributes for Squidex tokens.
Rule authors get more flexible fluid extensions, and error messages for background jobs are clearer in the UI.
SVG assets now carry svgWidth, svgHeight and viewBox as metadata, which is enough to size an SVG before it is loaded. Monitoring uses the correct version of Google Traces. Modal dialogs align properly, the buttons at the top right of each content field are positioned correctly, and a language without a display name shows a sensible name instead of a blank. The login screen separator was fixed, several texts and translations were corrected, a log message in a migration was fixed, and the npm packages were aligned to avoid version conflicts.
The full lists for 7.14.0 and 7.15.0 are in the changelog, and the documentation covers the AI tools, OIDC configuration and the content API headers in more detail.