@@ -0,0 +1,5 @@
+---
+"apostrophe": minor
+---
+
+Added the `@apostrophecms/ai:usage` event: one record per provider response, with its own token counts, and the ability to add attribution via the new `usageMetadata` option. This may be helpful in pricing and billing AI use by your own customers. Please note that the billing policies of AI providers are subject to change.
@@ -0,0 +1,7 @@
+---
+"apostrophe": patch
+---
+
+Security: the color field accepted any value that merely contained a valid `rgb()`, `hsl()` or similar color, so extra content before or after the color was stored as-is. When such a color is used by a widget style field rendered inline (no `selector`), that content reached the wrapper's `style` attribute and could inject HTML attributes into the published page. The whole value must now be a valid color, otherwise it is discarded like any other invalid color. Legitimate values (hex, named colors, `transparent`, `rgb()`/`rgba()`/`hsl()`/`hsla()` notations, CSS variable names) are stored unchanged. Exploitation requires permission to edit content using a color field (CWE-20, CWE-79, GHSA-vmgj-9cwm-cf3h).
+
+Thanks to [N.HARSHA VARDHAN](https://github.com/saiharsha0546-dot) for reporting the vulnerability.
@@ -0,0 +1,6 @@
+---
+"apostrophe": patch
+"@apostrophecms/apostrophe-astro": patch
+---
+
+Fields rendered in place with `AposField` in a widget can be edited as soon as the widget is added or saved in Astro, rather than only after the page is refreshed. Rich text fields in such a widget no longer appear as escaped markup during live preview and inline editing. Empty fields of a widget that was just saved can be selected and edited on the page right away, as they can be in a Nunjucks or JSX project.
@@ -0,0 +1,6 @@
+---
+"apostrophe": minor
+"@apostrophecms/apostrophe-astro": minor
+---
+
+Astro now routes literal content files such as `robots.txt` and `llms.txt` to the right site in multisite projects, using the new `literalRoutesScope` option of `@apostrophecms/url`.
@@ -0,0 +1,5 @@
+---
+"apostrophe": patch
+---
+
+Page data sent to Astro and other external fronts no longer includes `bestPage`, which only serves to populate `page` and made the payload a third larger; use `page` instead. A project that still needs it can restore it by extending the `pruneDataForExternalFront(req, template, data, moduleName)` method of `@apostrophecms/template` and setting `data.bestPage = req.data.bestPage`.
@@ -0,0 +1,5 @@
+---
+"apostrophe": patch
+---
+
+Fixed icon-only widget breadcrumb operations, such as the Styles button on a layout column, being announced by screen readers as "Provide a Button Label". These buttons now take their accessible name from the operation's `label`, or from its `tooltip` when no label is set. This also covers breadcrumb operations added by project code.
@@ -0,0 +1,5 @@
+---
+"apostrophe": minor
+---
+
+The Anthropic and OpenAI AI adapters now default to Claude Haiku 5.5, Sonnet 5.5 and Opus 5.5, and to GPT-6 Luna and GPT-6.1 Sol.
@@ -0,0 +1,7 @@
+---
+"@apostrophecms/import-export": patch
+---
+
+Security: the `clean-export` and `override-duplicates` routes did not require a login. Also, `clean-export` would discard the pending files of an import started by someone else and mark any import job as completed, without checking who owned either. Both routes now require a logged-in user. `clean-export` only acts on an import uploaded by the caller, and only ends that caller's own job. Import jobs are now recorded as belonging to the user who started them. Exposure was limited because the pending import's ID is random and only shown to the user who uploaded it, so in practice an attacker could only interfere with an import they could already identify (CWE-306, CWE-862, CWE-639, GHSA-rw26-wwfc-9wvm).
+
+Thanks to [Liuhuo Wan](https://github.com/CoSunshine) for reporting the vulnerability.
@@ -0,0 +1,6 @@
+---
+"apostrophe": patch
+"@apostrophecms/import-export": patch
+---
+
+Upgrade `csv-parse` to 7.x to address a security advisory.
@@ -0,0 +1,5 @@
+---
+"csv-to-zone-file": patch
+---
+
+Upgrade `csv-parse` to 7.x and stop installing ESLint as a runtime dependency, to address security advisories.
-Original file line number
+Diff line change
@@ @@ -0,0 +1,5 @@ @@
 +---
 +"apostrophe": minor
 +---
++
 +Added the `@apostrophecms/ai:usage` event: one record per provider response, with its own token counts, and the ability to add attribution via the new `usageMetadata` option. This may be helpful in pricing and billing AI use by your own customers. Please note that the billing policies of AI providers are subject to change.