docs: update for gtx-cli@2.14.7, gt-next@6.16.0, gt-react@10.18.0, gt-sanity@2.0.3#227
Open
moss-bryophyta wants to merge 1 commit intomainfrom
Open
docs: update for gtx-cli@2.14.7, gt-next@6.16.0, gt-react@10.18.0, gt-sanity@2.0.3#227moss-bryophyta wants to merge 1 commit intomainfrom
moss-bryophyta wants to merge 1 commit intomainfrom
Conversation
…-sanity@2.0.3 releases
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.
Summary
Docs updates reflecting the latest package releases from 2026-04-07.
gtx-cli@2.14.7— GT_API_KEY security fix (#1179)The setup wizard no longer prefixes
GT_API_KEYwith framework-specific client-exposure prefixes (VITE_,NEXT_PUBLIC_,GATSBY_,REDWOOD_ENV_). Production API keys must never be bundled into the client-side JavaScript.Files changed:
docs/en-US/cli/init.mdx— Added awarncallout in the Credentials section explaining thatGT_API_KEYis stored without a framework prefix and must remain server-side only. Clarifies thatGT_PROJECT_IDandGT_DEV_API_KEYretain their prefix as intended.docs/en-US/next/concepts/environments.mdx— Added awarncallout under the production environment variables section warning against usingNEXT_PUBLIC_GT_API_KEY, which would expose the production key in the client bundle.gt-next@6.16.0/gt-react@10.18.0/gt-node@0.5.0/gt-tanstack-start@0.4.0/gt-i18n@0.8.0— Context derivation (#1173)The compiler and CLI extractor now support
derive()inside the$contextprop of<T>components and the$contextoption ofuseGTstring calls. This generates a Cartesian product of content × context entries at build time, enabling context-aware translations.Files changed:
docs/en-US/next/concepts/compiler.mdx— Added a new "Context derivation" subsection under Features, with JSX and string examples showing howderive()works in$context.gt-sanity@2.0.3—@sanity/document-internationalizationnow an explicit dependency (#1177)@sanity/document-internationalizationis now a direct dependency ofgt-sanityrather than a peer dependency, so it no longer needs to be installed separately.Files changed:
docs/en-US/sanity/guides/quickstart.mdx— Added aninfocallout below the install block noting that@sanity/document-internationalizationis bundled withgt-sanityv2.0.3+ and installed automatically.Releases not requiring doc changes
gt@2.14.7— Empty release (dependency bump only)gt@2.14.6— Internal CLI/compiler changes for context derivation (covered above)gt@2.14.5— Bug fix: recursive string translation function resolution (internal, no API change)@generaltranslation/compiler@1.3.2— Bug fix: handle member expressions without throwing errors (internal)@generaltranslation/compiler@1.3.1— Internal support for context derivationgt-next@6.16.1— Dependency bump onlylocadex@1.0.140–142— Dependency bumps@generaltranslation/gt-next-lint@14.0.0–14.0.1— Dependency bumps@generaltranslation/python-extractor@0.2.7— Python context derivation (existing Python derive docs already cover this pattern)