unstale

npm / @blackwell-systems/gcf

@blackwell-systems/gcf

What changed in @blackwell-systems/gcf 2, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-19.

2 breaking2 new APIs and options2 behavior and defaults1 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli 0.2.8 on npm

@blackwell-systems/gcf 27 changes

Breaking changes 2

  • The default encode path writes a scalar shared by every record of a top-level tabular array once in the header and drops it from rows; decoding support is mandatory.

    2.7.0release notes

  • A double at or above 2^53 renders in exponent notation to align formatting with the numeric domain.

    2.6.0release notes

New APIs and options 2

  • Adds opt-in value-grouping for a keyed set by a low-cardinality column; decoding support is mandatory.

    2.7.0release notes

  • Adds a decode option for in-domain integers beyond JavaScript’s 2^53 safe range, with error as the default and string, bigint, or number alternatives.

    2.6.0release notes

Behavior and default changes 2

  • A bigint is accepted and serialized on encode.

    2.6.0release notes

  • Integers use signed int64 and non-integers use IEEE-754 double; integer literals decode exactly, and values outside int64 are rejected on decode and encode.

    2.6.0release notes

Fixes and other changes 1

  • Quoted keys containing [ alongside an array value now round-trip; the decoder locates the array count bracket after the closing quote.

    2.6.1release notes