Bump @sourcemeta/jsonschema from 16.10.0 to 17.0.0 in /vscode

[dependabot]

Bumps @sourcemeta/jsonschema from 16.10.0 to 17.0.0.

Release notes

Sourced from @​sourcemeta/jsonschema's releases.

v17.0.0

What's Changed

• Add colouring and modern formatting to the test, validate, metaschema, fmt, and install commands by @​HarshPopat23 in sourcemeta/jsonschema#874, sourcemeta/jsonschema#876, sourcemeta/jsonschema#877, sourcemeta/jsonschema#878, and sourcemeta/jsonschema#883
• Reject non-2020-12 schemas up front in codegen by @​jviotti in sourcemeta/jsonschema#880
• Loudly reject JSONL on fmt and lint --fix by @​jviotti in sourcemeta/jsonschema#885
• Fully support YAML on fmt and lint --fix by @​jviotti in sourcemeta/jsonschema#884
• Reject unsupported OpenAPI versions in the lint command by @​jviotti in sourcemeta/jsonschema#887
• Add --indentation to bundle and upgrade by @​jviotti in sourcemeta/jsonschema#889

Experimental new additions

• Support bundling OpenAPI descriptions in the bundle command by @​jviotti in sourcemeta/jsonschema#891

Breaking Changes

• Make bundle/upgrade print YAML if the input was YAML by @​jviotti in sourcemeta/jsonschema#888
• Stop considering embedded resource identifiers in --resolve by @​jviotti in sourcemeta/jsonschema#882
  • This often introduces confusion. New behaviour also better aligns with https://one.sourcemeta.com
• Stop attempting to upgrade meta-schemas in upgrade by @​jviotti in sourcemeta/jsonschema#879
  • This means the --meta option in upgrade no longer exists

Full Changelog: sourcemeta/jsonschema@v16.12.0...v17.0.0

v16.12.0

What's Changed

• Add a branded header to CLI help by @​HarshPopat23 in sourcemeta/jsonschema#867
• Highlight command names in CLI help by @​HarshPopat23 in sourcemeta/jsonschema#868
• Style human-readable lint diagnostics by @​HarshPopat23 in sourcemeta/jsonschema#871
• Implement --valid/--invalid flags in validate by @​jviotti in sourcemeta/jsonschema#875

Full Changelog: sourcemeta/jsonschema@v16.11.0...v16.12.0

v16.11.0

What's Changed

• Match configuration resolve keys by canonical URI by @​jviotti in sourcemeta/jsonschema#819
• Prefer local --resolve entries over --http fetching by @​jviotti in sourcemeta/jsonschema#858
• Cover embedded identifiers in the stuck --http import path by @​jviotti in sourcemeta/jsonschema#860
• Support --trace/-t in the test command by @​magic-peach in sourcemeta/jsonschema#861
• Report a nonexistent decode input the same way every other command does by @​magic-peach in sourcemeta/jsonschema#862
• Resolve relative embedded $ids before skipping --http fetches by @​jviotti in sourcemeta/jsonschema#863
• Add terminal color policy to CLI help by @​HarshPopat23 in sourcemeta/jsonschema#864
• Support linting OpenAPI specifications by @​jviotti in sourcemeta/jsonschema#866
  • This is at this point an experimental feature! Would love any feedback!

New Contributors

• @​magic-peach made their first contribution in sourcemeta/jsonschema#861
• @​HarshPopat23 made their first contribution in sourcemeta/jsonschema#864

... (truncated)

Commits

• 7d34440 v17.0.0
• fe4951a Support bundling OpenAPI descriptions in the bundle command (#891)
• 1d708f8 Better reject unsupported OpenAPI versions in relevant commands (#890)
• e5a31e6 Make bundle/upgrade print YAML if the input was YAML (#888)
• a4255b5 Add --indentation to bundle and upgrade (#889)
• bc19283 Reject unsupported OpenAPI versions in the lint command (#887)
• d3656d1 Remove outdated unsupported YAML documentation comments (#886)
• 0698e15 Fully support YAML on fmt and lint --fix (#884)
• 5b8c9fd Loudly reject JSONL on fmt and lint --fix (#885)
• 3eecbab Add colour and styling to the install command (#883)
• Additional commits viewable in compare view

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)

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[augmentcode]

🤖 Augment PR Summary

Updates the VS Code extension’s @sourcemeta/jsonschema dependency from ^16.10.0 to ^17.0.0.
Brings upstream CLI improvements, including YAML formatting and OpenAPI linting, without changing the extension’s integration code.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 1 suggestion posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

Could you check the YAML support assumption invalidated by vscode/package.json:78? v17 adds YAML fmt support, but webview/src/components/FormatTab.tsx:51–65 still suppresses the formatting result/action and tells users that the bundled CLI cannot format YAML, even when fmt --check succeeds.

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}