Repository navigation
Bump github.com/ajevans99/swift-json-schema from 0.13.1 to 0.14.1 - #5
Merged
k3KAW8Pnf7mkmdSMPHz27 merged 1 commit intoSep 23, 2026
Conversation
Owner
|
@dependabot rebase |
Bumps [github.com/ajevans99/swift-json-schema](https://github.com/ajevans99/swift-json-schema) from 0.13.1 to 0.14.1. - [Release notes](https://github.com/ajevans99/swift-json-schema/releases) - [Commits](ajevans99/swift-json-schema@v0.13.1...v0.14.1) --- updated-dependencies: - dependency-name: github.com/ajevans99/swift-json-schema dependency-version: 0.14.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/swift/github.com/ajevans99/swift-json-schema-0.14.1
branch
from
September 23, 2026 16:36
cf2d36b to
27c5e98
Compare
k3KAW8Pnf7mkmdSMPHz27
added a commit
that referenced
this pull request
Sep 23, 2026
Dependabot names Swift dependencies by their normalized repository URL, not by the bare package identity. The metadata block on its commits shows this: 2682f8f (PR #4): dependency-name: github.com/apple/swift-log cf2d36b (PR #5): dependency-name: github.com/ajevans99/swift-json-schema Group patterns are matched against the whole name (the wildcard matcher anchors with ^...$), so the bare `swift-log` and `swift-argument-parser` patterns never matched anything. That is why PR #4 was opened on its own, with no `dependency-group:` line in its metadata, even though a 1.14.0 -> 1.15.1 bump is a minor update the group's update-types allow. Use the full names so the apple-swift group picks up both packages. Full names are preferred over `*swift-log`-style globs, which could also match a fork or an unrelated package with the same suffix.
k3KAW8Pnf7mkmdSMPHz27
deleted the
dependabot/swift/github.com/ajevans99/swift-json-schema-0.14.1
branch
September 23, 2026 16:47
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.
Bumps github.com/ajevans99/swift-json-schema from 0.13.1 to 0.14.1.
Release notes
Sourced from github.com/ajevans99/swift-json-schema's releases.
... (truncated)
Commits
1514dd2Fix Draft 2020-12 projection parity for legacy recursive keywords (#201)88abaf2docs: clarify count constraint error bound payloads (#200)538710afeat!: preserve JSON number literals and support exact Decimal parsing (#198)c650a95Expand JSONSchema benchmarks with pinned real-world corpora (#186)8175498test: cover validation result serialization fidelity (#189)f7cdfc6Expand OrderedJSON throughput and Foundation round-trip benchmarks (#185)15ab456fix: isolate state when reusing Schema concurrently (#195)cfbc0a7fix: select compatible@Schemableinitializer overloads (#194)ab0745eAdd reproducible benchmark baselines and CI checks (#172)9975d1ffix: preserve reference and meta-schema initialization when decoding Schema (...