Published-release documentation · 281 actions; release compatibility · contract 5520b0fa9525

Documentation Version

The current site documents ggaction 0.0.17 with a published-release contract. A published-release contract matches that package version. A development contract can include newer behavior; its package version alone does not establish API availability. Each action entry identifies its release availability. The comparison baseline below is the older release used by the migration notes.

Choose the matching documentation

• Read the v0.0.13 release documentation at its immutable commit when using that installed release.
• Use this site’s action entries for the contract shown above. Each entry identifies the release that provides the action or explicitly marks it as development-only.
• Review the changelog and migration notes when upgrading.

The machine-readable provenance manifest records the same contract fingerprint, runtime source revision, baseline, and action availability. The full LLM bundle and its section manifest carry that identity too. The fingerprint covers runtime code, declarations, and public package configuration; documentation edits alone do not change the chart API fingerprint.

Migration from v0.0.13

Check your installed declarations before using encodeChannels, focused derived-data editors, normalization/completion/imputation, selected-label editors, or the new guide component editors. A method absent from your installed release will not become available by copying a newer example.

Source datasets remain immutable. Transform edits require a stable owner target and reject unchanged requests. Downstream transforms reject edits by default; explicitly request dependents:"recompute" to rebuild them. Creating replacement source rows uses a new dataset, followed by a supported owner edit or independent mark rebind.

Display label maps retain raw category identity. Numeric or temporal formatter tokens must match the scale field type. Explicit label text does not rename categories for selection, grouping, or scale-domain lookup.

Field-driven stroke has its own scale and legend, independent from fill/color. Point size ranges express area, and switching to a discrete size family requires the new domain and nondecreasing area range. encodeColor({ value }) is not a constant fill assignment; use the mark’s style editor or the supported stroke/opacity channel forms described in their references.