Skip to content

chore(deps): update dependency @decimalturn/toml-patch to v3 - #286

Open
renovate[bot] wants to merge 1 commit into
latestfrom
renovate/decimalturn-toml-patch-3.x
Open

chore(deps): update dependency @decimalturn/toml-patch to v3#286
renovate[bot] wants to merge 1 commit into
latestfrom
renovate/decimalturn-toml-patch-3.x

Conversation

@renovate

@renovate renovate Bot commented Aug 15, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@decimalturn/toml-patch 2.0.13.0.2 age confidence

Release Notes

DecimalTurn/toml-patch (@​decimalturn/toml-patch)

v3.0.2

Compare Source

Fixed
  • Patching: add an element to an inline array of tables (xs = [{ ... }]) as an inline element rather than emitting a [[xs]] section alongside it, which defined the key twice. ([#​267])
  • Patching: match a sibling's inner trailing comma when adding an inline table to an array, instead of taking it from the array's own separator ({ z = 0, } beside { a = 1 }). ([#​267])
  • Patching: match sibling bracket spacing when adding an inline table to an inline array ({ z = 0 } beside { a = 1 }). ([#​270])
  • Patching: keep an implicit parent table as an empty header when its last child is removed ([a.b]{ a: {} } now produces [a] instead of an empty document). Covers both table ([a.b]) and array-of-tables ([[a.b]]) cases. ([#​270])
  • Patching: pair renames one target each, so collapsing several equal-valued keys onto one no longer emits a key with an empty name. Keys sharing a value are matched in order, keeping their comments, and only the leftovers become removes or adds. ([#​269])
  • Patching: rename a [table] section key instead of throwing. The rename path read the key node directly, which only works for a key-value — a section wraps it in a TableKey. ([#​269])
  • Patching: rename a segment of a dotted section key (e.g. [a.b][x.b], [a.b][a.y], [a.b.c][a.x.c]) instead of throwing. The Rename handler now falls back to key-prefix search and handles segment-count mismatches when the target is rendered as a plain nested key. ([#​269])
  • Patching: avoid extra blank line when the first array-of-tables entry is converted to a table in-place during implicit parent materialisation. ([#​271])
  • Stringify: prevent float-to-bigint type change on round-trip. Whole-number values exceeding Number.MAX_SAFE_INTEGER (e.g. 743000000000000000 from TOML 743e+15) are now always emitted with a decimal point so they stay as number on re-parse instead of being promoted to bigint. ([#​273])
  • Patching: modifying nested dotted-key values that change from a table to a scalar (e.g. a.b.c = 1a.b = 42 under [a.b]) no longer emits conflicting inline tables or misplaces the value. ([#​274])
  • Patching: adding a key to a nested table array element (e.g. [[a.b]]) no longer throws "Incompatible child type 'InlineItem'". ([#​274])
  • Patching: Move entire AOT entry + owned comments as a unit during reorder so comments follow their entries when updateOrder is enabled.
  • Patching: tighten empty single-line inline tables and propagate to parent containers ([#​276])
  • Patching: unwrap InlineArrayItem when inserting into nested inline array ([#​276])
  • Patching: adjust commented out kv behavior to match expected behavior of comment ownership rules ([#​277])
  • Patching: ensure inline container tightening for deletions ([#​278])

v3.0.1

Compare Source

Fixed
  • Parsing: reject surrogates in \UXXXXXXXX escapes. ([#​261])
  • Stringify/Patching: reject unpaired surrogates in string values and keys instead of emitting invalid UTF-8. ([#​261])
  • Patching: indent a new first element of a multi-line array to match its sibling rows instead of the opening bracket. ([#​263])
  • Patching: give each element its own row when inserting more than one into the same multi-line array in a single patch. ([#​264])
  • Patching: drop an array element's comment with it when the array is the value of a multi-line inline table key. ([#​264])
  • Patching: reclaim a removed section's blank separator, so deleting sections no longer accumulates blank lines. ([#​265])
  • Patching: stop reading the removal of a key whose value matches an untouched sibling as a rename onto that sibling, which emitted the key twice and produced invalid TOML. ([#​262])
  • Patching: remove an array-of-tables key entirely when it is deleted, instead of bringing it back as key = []. ([#​266])
  • Patching: re-materialise an emptied nested array-of-tables as a.b = [] rather than a root key quoted "a.b". ([#​266])

v3.0.0

Compare Source

Changed
  • BREAKING: Raise minimum supported Node.js version from >=14 to >=16.
  • Patching: introducing explicit comment ownership. Comments describing a key, table, array-of-tables entry or an element inside a multi-line array or inline table now travel with it when removed or reordered via patch(), instead of being left behind to describe whatever ends up in that spot. See docs/CommentOwnership.md. ([#​259])
  • Improve stringification performance ([0e66e68])
Added
  • TomlDocument: New parseDocument function that parses a TOML string into a TomlDocument
  • Patching: New updateOrder option in TomlFormat. When true, patch() reorders root key-values, section blocks and table-body rows to match the JS object's key order, carrying each entry's comments along. Off by default. Shapes not yet reordered are left in place and reported via console.warn. ([#​260])
Fixed
  • Patching: Ensure all elements of nested tables are preserved when using inlineTableStart is 2 or higher. ([#​253])
  • Patching: prevent whitespace errors when swaping keys between tables.
  • Patching: handle BigInt values in documents without throwing. ([#​255])
  • Patching: handle commented multiline arrays correctly when adding keys or emptying them. ([#​255])
  • Patching: fix wrong section nesting when replacing a table with a scalar value. ([#​255])
  • Patching: preserve key with inline empty array when emptying an array-of-tables. ([#​255])
  • Patching: fix Node not found errors on structural type replacements like nested table-to-scalar and AOT-to-scalar. ([#​255])
  • Patching: fix remaining structural type replacement bugs — offset corruption when removing multiple sibling tables/AOTs, outer key loss when replacing a table/AOT with an inline object, and errors converting an array-of-tables to a plain array.
  • Patching: preserve +nan / -nan sign through parse and round-trip. ([#​255])
  • Patching: keep a regenerated root key at root level when a section header survives alongside it — emptying an array-of-tables appended the key past the header, which silently reparented it into that section. ([#​260])

v2.1.0

Compare Source

Added
  • Parsing: New temporal option in ParseOptions. When true, TOML date/time values are returned as Temporal objects (Temporal.PlainDate, Temporal.PlainTime, Temporal.PlainDateTime, Temporal.ZonedDateTime) instead of custom Date subclasses.
  • Stringify: Auto-detect Temporal objects in the input JS and serialize them to the correct TOML date/time type. Note that ZonedDateTime with IANA timezone annotations will throws an error (TOML only supports numerical offsets).

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "on the 15th day of the month"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Added@​decimalturn/​toml-patch@​3.0.210010010095100

View full report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants