chore: release#411
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 18, 2026 23:01
a82e2be to
f30507a
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
[email protected]
Patch Changes
344e929Thanks @bmatge! -dsfr-data-query: l'order-by(et le group-by/where) n'est plus délégué entri serveur quand la chaîne entre la query et la source qui fetch contient un
transformateur qui crée ou renomme des colonnes —
dsfr-data-unpivot(toujours) ou
dsfr-data-normalizeavecrename/compute/flatten/lowercase-keys. Les opérations de la query s'expriment dans le schémaPOST-transformation : les pousser au serveur envoyait des noms de colonnes
inconnus de l'API (Grist Records :
?sort=annee→ 500unknown key) etmettait la source partagée en erreur pour tous ses abonnés. Le tri s'exécute
désormais côté client, sur les données transformées (#394). Nouveau hook
optionnel
transformsSchema()sur le contratSourceElement.