Skip to content

Bump js-yaml from 4.2.0 to 5.0.0 in /extensions/ql-vscode#4438

Open
dependabot[bot] wants to merge 3 commits into
mainfrom
dependabot/npm_and_yarn/extensions/ql-vscode/js-yaml-5.0.0
Open

Bump js-yaml from 4.2.0 to 5.0.0 in /extensions/ql-vscode#4438
dependabot[bot] wants to merge 3 commits into
mainfrom
dependabot/npm_and_yarn/extensions/ql-vscode/js-yaml-5.0.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 26, 2026

Copy link
Copy Markdown
Contributor

Bumps js-yaml from 4.2.0 to 5.0.0.

Changelog

Sourced from js-yaml's changelog.

[5.0.0] - 2026-06-20

Added

  • Added named exports for schemas, tags, parser events and AST utilities.
  • Reworked JSON_SCHEMA and CORE_SCHEMA with spec-compliant scalar resolution rules, and added YAML11_SCHEMA.
  • Added realMapTag for lossless mappings with non-string and complex keys. Object-based mappings now reject complex keys instead of stringifying them.
  • Added dump() transform option for changing the generated AST before rendering.
  • Added dump() options seqInlineFirst, flowBracketPadding, flowSkipCommaSpace, flowSkipColonSpace, quoteFlowKeys, quoteStyle and tagBeforeAnchor.
  • Added formal data layers (events and AST) for modular data pipelines.
    • Added low-level parser (to events), presenter and visitor APIs.
  • Added the YAML Test Suite to the test set.

Changed

  • See the migration guide for upgrade notes.
  • Rewritten in TypeScript and reorganized the public API around flat named exports.
  • Reduced the set of exported schemas:
    • YAML 1.2 schemas: CORE_SCHEMA (loader default), JSON_SCHEMA, FAILSAFE_SCHEMA.
    • YAML11_SCHEMA, a combination of all YAML 1.1 tags (YAML 1.1 does not specify a schema, only "types").
  • load/dump default behaviour is now specified exactly via schemas:
    • load uses CORE_SCHEMA, without !!merge by default.
    • dump uses YAML11_SCHEMA + CORE_SCHEMA for the quoting check, to guarantee backward compatibility by default.
  • !!set is now loaded as a JavaScript Set.
  • Replaced the Type API with a tags API. Similar, but more precise and simpler. See examples for details. Tags can be defined via defineScalarTag(), defineSequenceTag() and defineMappingTag(), or as a spread + override of an existing tag.
  • Renamed Schema.extend() to Schema.withTags().
  • Expanded YAML 1.2 conformance and improved handling of directives, document markers, block keys, multiline scalars, tag syntax and other things.
  • load() now throws on empty input instead of returning undefined.
  • Moved browser builds to the js-yaml/browser export.
  • Deprecated the loadAll signature with an iterator (still works, but is a candidate for removal).

Removed

  • Removed deprecated safeLoad(), safeLoadAll() and safeDump() exports.
  • Removed DEFAULT_SCHEMA and the nested types export.
  • Removed loader options onWarning, legacy and listener.
  • Removed dumper options styles, replacer, noCompatMode, condenseFlow, quotingType and forceQuotes. Renamed noArrayIndent to seqNoIndent. Formatting and representation are now configured through presenter options,

... (truncated)

Commits
  • 75148bc 5.0.0 released
  • 704b25d Quote document markers followed by whitespace
  • 42dea28 Support complex !!pairs keys with realMapTag
  • 6cf374e Fix dumping strings that collide with YAML markers
  • 65b8d94 Clarify !!omap/!!pairs support
  • 33e3640 Move tagname helpers to common/ and remove unused exports
  • 4dd582b Cleanup export types
  • 39b3792 Add types export
  • 0cd01e9 docs: update for v5
  • c5a61a4 Fix presenter coverage
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 4.2.0 to 5.0.0.
- [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md)
- [Commits](nodeca/js-yaml@4.2.0...5.0.0)

---
updated-dependencies:
- dependency-name: js-yaml
  dependency-version: 5.0.0
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the Update dependencies Dependabot update PRs label Jun 26, 2026
@dependabot dependabot Bot requested a review from a team as a code owner June 26, 2026 08:11
@dependabot dependabot Bot added the Update dependencies Dependabot update PRs label Jun 26, 2026
Copilot AI requested a review from josefs June 29, 2026 10:15
@dependabot @github

dependabot Bot commented on behalf of github Jun 30, 2026

Copy link
Copy Markdown
Contributor Author

A newer version of js-yaml exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

…tem on Windows

The `handleRemoveHistoryItem` method called `getCurrent()` after several async
operations. On Windows, VS Code fires `onDidChangeSelection` asynchronously
during awaits (after `refresh()` from `remove()`), which could change the
current item to an unexpected value before `getCurrent()` was called.

Fix by:
1. Capturing the current item *before* any async operations in
   `handleRemoveHistoryItem`, and restoring it afterwards if the item is still
   in history (i.e. it was not one of the removed items). Also add an explicit
   `setCurrentItem(current)` call before `reveal` to sync the internal state in
   case a deferred `onDidChangeSelection` changed it during the awaits.
2. Mocking `showInformationMessageWithAction` in the test to return immediately
   instead of calling the real VS Code API, which could trigger additional async
   event processing.

Fixes the failing "Test (windows-latest)" CI job:
  QueryHistoryManager › handleRemoveHistoryItem › when the item is a variant
  analysis › when in progress › when the item being removed is not selected
  › should not change the selection
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Update dependencies Dependabot update PRs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant