Release notes for release/1.348.0 - #1415
Merged
Merged
Conversation
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
rmagier1
approved these changes
Sep 4, 2026
The generated note carried one Internal:-prefixed bullet about the gated
note v2 refactor and nothing else, missing the release's only
customer-facing change: canvas-plugins 0.219.0 (KOALA-6954) removed the
stored body field from the SDK Note model and replaced it with a
read-only property backed by a custom queryset.
Reading body is unchanged, but filter/exclude/get/only/defer are now the
only operations that can name it. values("body") and values_list("body")
raise FieldError, and order_by plus cross-model traversal no longer
resolve. Records that on the Note data page under a new "Querying on the
body" section and links the release note at it.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The generator dated it 09.04, cut-day + 1, which is a Friday. Moving it to the actual ship day. Renaming is safe for URLs: the page and the feed entry id both come from the version slug, /release-notes/1-348-0, not the date. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Verified against canvas-plugins 0.219.0 that naming body through a
relation now raises: Appointment.objects.defer("note__body") gives
FieldDoesNotExist, and filter(note__body=...) gives FieldError. Five
customer plugin files do exactly the first one, so this is a real break
rather than a theoretical one.
Tags the release breaking-change and prefixes the bullet to match the
1.210.0 precedent, and adds a warning alert on the Note page pointing
affected plugins at querying Note separately.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
"Used to work and no longer does" leaves a reader guessing which release to check against. Name the date and link the release note, so the authoritative date stays in one place if the ship date moves again. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Everything in the SDK data module is read-only, so calling body a "read-only property" implies a contrast with writable attributes that do not exist. The distinction that matters is computed on access versus stored in a column, which is what drives the query limits. Also scopes the release note and its digest to the SDK data module, so neither reads as a change to the note body generally. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The whole data module is read-only, so labelling individual attributes and models that way implies a contrast with writable ones that do not exist. Attribute tables now say (computed) where the value is derived rather than stored, which is the distinction that actually affects what a plugin can do with it, and the "X is a read-only data model" sentences are gone from Invoice, EducationalMaterial, RefillRequest and PrescriptionChangeRequest. ContentType and PluginCommand now say they expose their models rather than "provide read-only access" to them. data.md keeps the one module-level statement, which is where the fact belongs. RefillRequest's `ignored` note is reworded rather than dropped: that a plugin can filter on it but not dismiss a request through the model is worth saying, just not as a consequence of "read-only". Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The digest labelled only the relation lookup, but values("body"),
values_list("body") and order_by("body") equally used to work and now
raise — synapticure's plugin breaks on exactly that one. Both digest
bullets now say Breaking.
In the note, the same label goes on the values/sorting sub-bullet, and
the two breaks now sit together ahead of the "still works" one, so the
warnings read as a pair rather than being split by it.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
jamagalhaes
force-pushed
the
release/1.348.0
branch
from
September 8, 2026 09:56
f86b7aa to
b97e8b8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Auto-generated release notes for release/1.348.0.