[Snyk] Upgrade yaml from 1.10.2 to 2.1.3 #3
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.
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade yaml from 1.10.2 to 2.1.3.
ℹ️ 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.
Warning: This is a major version upgrade, and may be a breaking change.
Release notes
Package name: yaml
-
2.1.3 - 2022-10-05
- Set correct node-end position for block collections with comments (#413)
-
2.1.2 - 2022-10-02
- Set correct node-end position for empty values with comments (#413)
-
2.1.1 - 2022-05-29
- Revert "Use TS named tuple for range (#385)" -- see #393
- Fix types for compatibility with TS 4.2 and 4.7
- Add CI workflow for testing published type in a range of TS versions
-
2.1.0 - 2022-05-14
- Improve/specify/fix TS types for Document & collection access methods (#383)
- Use TS named tuple for range (#385)
- Rename internal Document option as
- Update tsc target to ES2020 to match Node.js support
- Update dev dependencies, including jest 28
-
2.0.1 - 2022-04-15
- Fix tags and anchors on map keys (#378)
-
2.0.0 - 2022-04-06
-
2.0.0-11 - 2022-03-22
- Add warning for aliases & anchors ending with a colon (#370)
- Add
- Add
- Flow collection keys in block maps (redhat-developer/vscode-yaml#712)
- Error on %YAML directives with content after version (#348)
- Use correct check for empty null source (#366)
- Do not throw during composition, even for bad tokens (#367)
- Error on invalid
- Empty block scalars with chomp=keep & trailing whitespace
- Parse
- Do not consider tabs as indent for flow collections
- Include trailing more-indented empty lines in block scalar contents
- Should complain about
- Update dev dependencies, including
- Update
- Don't needlessly skip yaml-test-suite
- test-events: Do not skip events for only apparently empty documents
- yaml-test-suite: Skip
-
2.0.0-10 - 2021-12-31
- The TS type of
- Add
- Add
- Add
- Allow for
- Add
- Update to latest
- Add
- Use
- Allow for custom schemas in TS types (#325)
- Flow collection expected-end error (#328)
- parser:
- Handle duplicate flow
- Correctly stringify non-finite scalars with
- Allow block map with flow collection key as explicit key
- Do not use negative indent for any parser tokens
-
2.0.0-9 - 2021-11-13
- Add
- Allow for custom schema id, provided that
- Expose tags & types required by custom composers (#325)
- cst: Specify
- lexer: Reset flow-key flag on comma in flow collection (#316)
- lexer: Allow unindented comment in flow collection
- Support seq-of-maps merge key values (#321)
- compose: Indent level of empty block scalars with keep chomping (#313)
- Honor
- Get rid of extra whitespace around empty map values
- Drop ...expansion from public TS interfaces (#334)
-
2.0.0-8 - 2021-09-06
- Add a new createNode option
- Add
- lexer: Cache line end positions (#298)
- Handle
- Allow for collection
- Fix parsing errors with CRLF line endings (#306, #307)
-
2.0.0-7 - 2021-07-17
-
2.0.0-6 - 2021-06-14
-
2.0.0-5 - 2021-04-18
-
2.0.0-4 - 2021-03-13
-
2.0.0-3 - 2021-01-31
-
2.0.0-2 - 2021-01-31
-
2.0.0-1 - 2020-10-05
-
2.0.0-0 - 2020-08-23
-
1.10.2 - 2021-03-13
from yaml GitHub release notesNo changes in executable code, only TS types.
Fixes for TypeScript users. Arguably this could've been a patch release as well.
_directivesto resolve type conflict with ToString options (#389)Read more
This version of
yamlhas been published to npm using thenextdist-tag, so install it with:BREAKING CHANGES
YAML.defaultOptionsis removed (#346)For a while, it's been undocumented, but still available. Since the options refactor of #235, it has only provided defaults for Parse & Document options, and not any of the others, so its name is a bit misleading as well.
If you're using
YAML.defaultOptions, you'll need to explicitly set the options in the appropriateparse*()andnew Document()calls after this change.directives.markeris renamed asdirectives.docStart(#371)The behaviour of the property stays the same as before.
New Features
directives.docEnd, for...marker (#371)YAML.visitAsync()(#372)Bugfixes
%YAMLdirectives? : xas { ? { : x } }-,and-]in flow collections@ types/nodedowngradeTest Improvements
yaml-test-suite, skipping some new testsB63Ptestin.jsontests when expecting errorsThis version of
yamlhas been published to npm using thenextdist-tag, so install it with:BREAKING CHANGES
doc.directivesnow indicates it as optional. Its actual value has not changed, but the type needs to account for what might happen ifdoc.setSchema()is called with anullversion argument. (#344)New Features
Add a compatibility checker (#335)
Adds a new schema option
compat: string | Tags. If set, warns during composition about compatibility issues with the given schema. When stringifying, uses scalar styles that are parsed correctly by thecompatschema as well as the actual schema.Support for Non-YAML Schemas
While YAML is a superset of JSON, it isn't a strict superset of other JSON-based configuration languages. Feature-wise, though, these languages are as a rule a subset of YAML features, so let's build some groundwork for supporting them as well by making additional aspects of this library configurable.
commentStringoption, refactor internals to support it (#336)toStringDefaultsoption (#337)collectionStyleoption (#343)Schemainstance as schema option (#344)Test Improvements
json-test-suiteas git submodule (#340)yaml-test-suitedata{}and[]indicators to flow maps & sequences in test-events output (used by the YAML Test Matrix)--target es5intest:dist:typesscript (#334)Bugfixes
flow-error-endtoken should not advance offset:indicators correctlyformat: 'EXP'This version of
yamlhas been published to npm using thenextdist-tag, so install it with:Hopefully the breaking change for
singleQuote: falsewon't cause anyone issues. Otherwise, small improvements only.BREAKING CHANGES
Allow disabling single & block quotes completely (#326)
The options for representing scalar values are refactored, such that
blockQuote(new) andsingleQuote(expanded) allow setting a preference as well as preventing said styles from being used at all. This changes howsingleQuote: falseis handled. To retain the previous behaviour, usesingleQuote: nullor leave the option unset.New Features
keepSoureTokenparse option, addingsrcTokenvalues to Nodes (#309)customTagsis defined (#325)Bugfixes
resolveAsScalarreturn typesingleQuoteoption more widelyThis version of
yamlhas been published to npm using thenextdist-tag, so install it with:This release doesn't really do anything major, it's really just an accumulation of small things over the past few weeks.
New Features
aliasDuplicateObjects(#299)clone()methods to Document, Directives, Schema and all Nodes (#304)Bugfixes
doc.createNode(doc)the same asdoc.createNode(doc.contents)(#303)setIn()to handle objects, including duplicatesCommit messages
Package name: yaml
Compare
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:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs