[INTERNAL] Bump @apidevtools/json-schema-ref-parser from 13.0.5 to 14.1.1 - #1080
Merged
dependabot[bot] merged 1 commit intoJul 21, 2025
Conversation
Bumps [@apidevtools/json-schema-ref-parser](https://github.com/APIDevTools/json-schema-ref-parser) from 13.0.5 to 14.1.1. - [Release notes](https://github.com/APIDevTools/json-schema-ref-parser/releases) - [Commits](APIDevTools/json-schema-ref-parser@v13.0.5...v14.1.1) --- updated-dependencies: - dependency-name: "@apidevtools/json-schema-ref-parser" dependency-version: 14.1.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
|
The |
dependabot
Bot
added
dependencies
d3xter666
approved these changes
Jul 21, 2025
d3xter666
left a comment
d3xter666
left a comment
Member
There was a problem hiding this comment.
@dependabot squash and merge
dependabot
Bot
deleted the
dependabot/npm_and_yarn/apidevtools/json-schema-ref-parser-14.1.1
branch
July 21, 2025 06:17
d3xter666
pushed a commit
that referenced
this pull request
Sep 24, 2025
…edLocales (#1080) This fixes two problems that could have occurred: A properties file with an invalid locale was still taken into the list of supported locales, which then caused a runtime exception in the ResourceBundle as it validates the input. Another problem was that properties files could have a valid name according to BCP47, but the file won't be ever requested with that name. This is due to the fact that the ResourceBundle does use the legacy Java locale format (using underscores instead of dashes) for the request URL. In both cases, the properties file is now ignored and no entry for the supportedLocales is created. Only locales that are valid according to the legacy Java locale format are considered. However, there is one special case: sr_Latn is also requested by the UI5 runtime, although it contains a BCP47 script, which is not valid according to the legacy Java locale format. --------- Co-authored-by: Merlin Beutlberger <m.beutlberger@sap.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Bumps @apidevtools/json-schema-ref-parser from 13.0.5 to 14.1.1.
Release notes
Sourced from
@apidevtools/json-schema-ref-parser's releases.... (truncated)
Commits
c1b2916fix(bundle): don't look for a$refpointer on a null value (#393)dfbf4bbfeat: addonBundlecallback (#391)6c77265fix(targets): upgrade targets to support Node 20 (current maintenace node), c...3c7af41chore(deps): update deps, set typescript type flag9376c24chore(deps): bump deps3406a25fix(file): support trailing slashes in file resolver #389171e30ffix(options): make safe url resolver optional and boolean0ac9f35chore(tests): skip url safety resolver in browser5ffea78fix(safety): assume browsers are safe urls932683fchore: depsDependabot 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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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)