Update dependency js-toml to v1.2.1 #34

Merged

MarkerBot merged 1 commit from renovate/js-toml-1.x-lockfile into main

2026-07-08 04:01:14 -07:00

MarkerBot commented

2026-07-08 04:00:50 -07:00

Member

This PR contains the following updates:

Package	Change	Age	Confidence
js-toml	`1.1.3` → `1.2.1`

Release Notes

sunnyadn/js-toml (js-toml)

`v1.2.1`

Compare Source

Fixed

Dates with years below 100 (e.g. 0001-01-01T00:00:00Z) were rejected or mis-parsed via JavaScript's legacy Date year mapping; they now parse correctly.
Out-of-range UTC offsets (+25:00, +12:60) were accepted; they are now rejected per RFC 3339.
Duplicate super-table headers ([a.b] then [a] twice) were accepted; redefinition is now an error per the spec.

Changed

The vendored toml-test suite is upgraded to the official v2.2.0 TOML-1.1.0-gated set (332 → 681 cases, zero exclusions).

`v1.2.0`

Compare Source

Added

TOML v1.1.0 support, enabled by default (spec changelog):
- Inline tables may span multiple lines, contain comments, and end with a trailing comma (toml-lang/toml#904). Newlines are still rejected inside a key/value pair itself (around = or a dotted-key .), exactly as the spec ABNF requires.
- \xHH escapes in basic and multi-line basic strings, decoding to the Unicode code point U+00HH (toml-lang/toml#796).
- \e escape (U+001B) in basic and multi-line basic strings (toml-lang/toml#790).
- Seconds are optional in times and date-times (toml-lang/toml#894); omitted seconds are normalized to :00 (13:37 loads as "13:37:00"). Fractional seconds still require whole seconds per the spec ABNF.

Changed

Documents that were syntax errors under TOML 1.0.0 but are valid TOML 1.1.0 (see above) now parse successfully instead of throwing SyntaxParseError. Every valid TOML 1.0.0 document parses exactly as before.
dump() intentionally keeps emitting TOML v1.0.0-compatible output (single-line inline tables, no trailing commas, \uXXXX escapes, full-precision datetimes) so generated documents remain readable by 1.0-only parsers.

Configuration

📅 Schedule: (UTC)

Branch creation
- At any time (no schedule defined)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 has been generated by Mend Renovate.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [js-toml](https://github.com/sunnyadn/js-toml) | [`1.1.3` → `1.2.1`](https://renovatebot.com/diffs/npm/js-toml/1.1.3/1.2.1) | ![age](https://developer.mend.io/api/mc/badges/age/npm/js-toml/1.2.1?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/js-toml/1.1.3/1.2.1?slim=true) | --- ### Release Notes <details> <summary>sunnyadn/js-toml (js-toml)</summary> ### [`v1.2.1`](https://github.com/sunnyadn/js-toml/blob/HEAD/CHANGELOG.md#121---2026-07-08) [Compare Source](https://github.com/sunnyadn/js-toml/compare/v1.2.0...v1.2.1) ##### Fixed - Dates with years below 100 (e.g. `0001-01-01T00:00:00Z`) were rejected or mis-parsed via JavaScript's legacy `Date` year mapping; they now parse correctly. - Out-of-range UTC offsets (`+25:00`, `+12:60`) were accepted; they are now rejected per RFC 3339. - Duplicate super-table headers (`[a.b]` then `[a]` twice) were accepted; redefinition is now an error per the spec. ##### Changed - The vendored [toml-test](https://github.com/toml-lang/toml-test) suite is upgraded to the official v2.2.0 TOML-1.1.0-gated set (332 → 681 cases, zero exclusions). ### [`v1.2.0`](https://github.com/sunnyadn/js-toml/blob/HEAD/CHANGELOG.md#120---2026-07-08) [Compare Source](https://github.com/sunnyadn/js-toml/compare/v1.1.3...v1.2.0) ##### Added - [TOML v1.1.0](https://toml.io/en/v1.1.0) support, enabled by default ([spec changelog](https://github.com/toml-lang/toml/blob/1.1.0/CHANGELOG.md)): - Inline tables may span multiple lines, contain comments, and end with a trailing comma ([toml-lang/toml#904](https://github.com/toml-lang/toml/issues/904)). Newlines are still rejected inside a key/value pair itself (around `=` or a dotted-key `.`), exactly as the spec ABNF requires. - `\xHH` escapes in basic and multi-line basic strings, decoding to the Unicode code point U+00HH ([toml-lang/toml#796](https://github.com/toml-lang/toml/issues/796)). - `\e` escape (U+001B) in basic and multi-line basic strings ([toml-lang/toml#790](https://github.com/toml-lang/toml/issues/790)). - Seconds are optional in times and date-times ([toml-lang/toml#894](https://github.com/toml-lang/toml/issues/894)); omitted seconds are normalized to `:00` (`13:37` loads as `"13:37:00"`). Fractional seconds still require whole seconds per the spec ABNF. ##### Changed - Documents that were syntax errors under TOML 1.0.0 but are valid TOML 1.1.0 (see above) now parse successfully instead of throwing `SyntaxParseError`. Every valid TOML 1.0.0 document parses exactly as before. - `dump()` intentionally keeps emitting TOML v1.0.0-compatible output (single-line inline tables, no trailing commas, `\uXXXX` escapes, full-precision datetimes) so generated documents remain readable by 1.0-only parsers. </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, 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 has been generated by [Mend Renovate](https://github.com/renovatebot/renovate).

MarkerBot added 1 commit

2026-07-08 04:00:50 -07:00

Update dependency js-toml to v1.2.1

ci/woodpecker/push/build Pipeline was successful

Details

ci/woodpecker/pr/build Pipeline was successful

Details

ci/woodpecker/pull_request_closed/build Pipeline was successful

Details

f7bbb3be1e

MarkerBot scheduled this pull request to auto merge when all checks succeed

2026-07-08 04:00:51 -07:00