build(deps): bump js-yaml from 4.3.1 to 5.2.3 - #7
Conversation
51d4182 to
e4d1365
Compare
Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 4.3.1 to 5.2.3. - [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md) - [Commits](nodeca/js-yaml@4.3.1...5.2.3) --- updated-dependencies: - dependency-name: js-yaml dependency-version: 5.2.3 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
e4d1365 to
02b1cb6
Compare
|
Superseded by #17, which takes js-yaml 5.2.3 with the guards this upgrade needs rather than the version bump alone. Policy files are YAML and are attacker-adjacent input, so the upgrade was reviewed with a differential probe across the API surface this repo actually calls. Two operator-visible behaviour changes needed handling: an unparseable policy file must leave the previous ruleset in force, and an unparseable agent-harness config must degrade one dashboard panel rather than the dashboard. Both are now covered by tests. The version is also pinned exactly rather than by range, and |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps js-yaml from 4.3.1 to 5.2.3.
Changelog
Sourced from js-yaml's changelog.
... (truncated)
Commits
67404455.2.3 released94e766dUpdate changelogc3bd7caPolish previous commit, #78000209b6presenter: treat a tab-indented line in a folded scalar as more-indented (#780)40fcb4fFix missing mapping values before document markers and reject unpaired mappin...49280f3Fix !!timestamp resolution for years 0000-0099, #775355dc96fix: prevent prototype fallback in tag and harden object lookups, #782 (than...d524f83docs: add contributing guidelines3c295595.2.2 released3e5240fparser: avoid reparsing flow sequence pair keys