chore(deps): update giantswarm/schemalint action to v2.6.2 - #258
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update giantswarm/schemalint action to v2.6.2#258renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/giantswarm-schemalint-2.x
branch
from
July 29, 2026 16:31
b63acdf to
829025e
Compare
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
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 contains the following updates:
v2.6.1→v2.6.2Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
giantswarm/schemalint (giantswarm/schemalint)
v2.6.2Compare Source
Changed
cluster-apprule set: allowunevaluatedProperties: falseon a schema that also has$ref. This is the only way to reject unknown keys on a referenced object in draft2020-12 —
additionalPropertiesonly considers siblingproperties/patternProperties(2020-12 core, §10.3.2), so
additionalProperties: falsenext to a$refrejects everyfield the referenced schema defines and breaks
helm template. Every other use ofunevaluatedProperties, and all use ofunevaluatedItems, remains an error. Spellingsthat leave the object open anyway are not covered by the exception: an
additionalPropertiesthat is not
falseeither next to the$refor on the target it resolves to (both annotateevery property as evaluated), and a type that is not
object, taken from the$reftargetwhen the schema declares none.
cluster-apprule set: "Object should disable additional properties" no longer fires ona
$refclosed withunevaluatedProperties: false. Such an object is closed, andadding
additionalProperties: falseto it would be wrong. This applies to the$reftarget as well, which is reported at the same location as the referring schema.
cluster-apprule set: "Object must have at least one property" now counts propertiesreached through
$ref, so a schema that is only a$refto an object with propertiesno longer errors.
schemalint-windows-<arch>.exe.golang.org/x/systo v0.47.0, fixing CVE-2026-39824.github.com/santhosh-tekuri/jsonschemato v6. Findings on every schema underpkg/are unchanged, with two differences to be aware of. The wording of the "invalidJSON Schema" message for a schema that does not compile comes from the library. And
formatnow has to name a format the library knows: v5 accepted any name, soformat: something-made-upcounted as a constraint on a string, and no longer does.golang.org/x/textto v0.39.0, fixing CVE-2026-56852. jsonschema v6 pulls it in.Fixed
$refand its targetresolve to one location, so a rule that visits both reported it once per visit.
property instead of the root of the schema.
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.