Bump @sourcemeta/jsonschema from 15.9.0 to 16.0.0 in /vscode#201
Bump @sourcemeta/jsonschema from 15.9.0 to 16.0.0 in /vscode#201dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@sourcemeta/jsonschema](https://github.com/sourcemeta/jsonschema) from 15.9.0 to 16.0.0. - [Release notes](https://github.com/sourcemeta/jsonschema/releases) - [Commits](sourcemeta/jsonschema@v15.9.0...v16.0.0) --- updated-dependencies: - dependency-name: "@sourcemeta/jsonschema" dependency-version: 16.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
🤖 Augment PR SummarySummary: Updates the VSCode package dependency 🤖 Was this summary useful? React with 👍 or 👎 |
| "qna": "marketplace", | ||
| "dependencies": { | ||
| "@sourcemeta/jsonschema": "^15.9.0" | ||
| "@sourcemeta/jsonschema": "^16.0.0" |
There was a problem hiding this comment.
@sourcemeta/jsonschema v16.0.0 switches Linux/BSD binaries to dynamically loading system libcurl via dlopen; can you confirm the VSCode extension’s target environments (incl. remote/containers) reliably provide libcurl or that the extension surfaces a clear error/doc if it’s missing? Otherwise this upgrade could introduce runtime failures that won’t show up until users run the extension on minimal images.
Severity: medium
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
Bumps @sourcemeta/jsonschema from 15.9.0 to 16.0.0.
Release notes
Sourced from @sourcemeta/jsonschema's releases.
Commits
b52f6dfv16.0.0dda4f72Use systemlibcurlthroughdlopenon Linux/BSD (#781)fc125d6SupportdependentSchemasanddependentRequiredoncodegen(#780)f94a8ebSupport bundled schemas with custom meta-schemas (#779)73235b7v15.11.06648199Make use ofNSURLSessionandWinHTTPon macOS and Windows (#778)0fdc267Upgrade all Sourcemeta dependencies (#777)e8e8968Bring Going Further README section right below Usage20de62bv15.10.171ff30dFix crash on--default-dialectrelative path without$id(#776)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)