[Snyk] Upgrade structured-headers from 1.0.1 to 2.0.0 #7
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.
Snyk has created this PR to upgrade structured-headers from 1.0.1 to 2.0.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 3 versions ahead of your current version.
The recommended version was released on a month ago.
Release notes
Package name: structured-headers
The "Structured Field Values" was updated in RFC9651. This new specification added the 'Date' and 'Display String' field type, which encode unix timestamp and Unicode string respectively.
Perfect time to update this package as well! This new major release supports the new standard, and also has a few other changes:
ArrayBuffer
instead of a custom ByteSequence object. This is a breaking change.Date
andDisplayString
from RFC9651.node:assert
.node:test
.exports
value inpackage.json
. (@ CxRes)Date
andDisplay String
types, from the new draft draft-ietf-httpbis-sfbis.TypeError
or a plainError
in a few places in the parser, where it should have beenParseError
this is corrected everywhere now.Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: