chore(deps): bump referencing from 0.30.2 to 0.35.1 in /application

[dependabot]

Bumps referencing from 0.30.2 to 0.35.1.

Release notes

Sourced from referencing's releases.

v0.35.1

• Make Resource.pointer also properly handle empty pointers (which refer to the root document). This fix likely only affects you if you were using that function directly, as Resource.lookup already handles empty fragments.

Full Changelog: python-jsonschema/referencing@v0.35.0...v0.35.1

v0.35.0

• Ensure that Registry.contents() also raises NoSuchResource exceptions for nonexistent resources, not KeyError (which is an implementation detail).

Full Changelog: python-jsonschema/referencing@v0.34.0...v0.35.0

v0.34.0

What's Changed

• Also look inside definitions keywords even on newer dialects. The specification recommends doing so regardless of the rename to $defs.
• Ensure non-blocking mypy compatibility by @​jamescw19 in python-jsonschema/referencing#130

New Contributors

• @​jamescw19 made their first contribution in python-jsonschema/referencing#130

Full Changelog: python-jsonschema/referencing@v0.33.0...v0.34.0

v0.33.0

• Add a referencing.jsonschema.SchemaResource type alias to go along with the other JSON Schema specialized types.

Full Changelog: python-jsonschema/referencing@v0.32.1...v0.33.0

v0.32.1

• Make Specification.detect raise a CannotDetermineSpecification error even if passed a mapping with a $schema key that doesn't match JSON Schema dialect semantics (e.g. a non-string).

Full Changelog: python-jsonschema/referencing@v0.32.0...v0.32.1

v0.32.0

Full Changelog: python-jsonschema/referencing@v0.31.1...v0.32.0

v0.31.1

... (truncated)

Changelog

Sourced from referencing's changelog.

v0.35.1

• Make Resource.pointer also properly handle empty pointers (which refer to the root document). This fix likely only affects you if you were using that function directly, as Resource.lookup already handles empty fragments.

v0.35.0

• Ensure that Registry.contents() also raises NoSuchResource exceptions for nonexistent resources, not KeyError (which is an implementation detail).

v0.34.0

• Also look inside definitions keywords even on newer dialects. The specification recommends doing so regardless of the rename to $defs.

v0.33.0

• Add a referencing.jsonschema.SchemaResource type alias to go along with the other JSON Schema specialized types.

v0.32.1

• Make Specification.detect raise a CannotDetermineSpecification error even if passed a mapping with a $schema key that doesn't match JSON Schema dialect semantics (e.g. a non-string).

v0.32.0

• Add Specification.detect, which essentially operates like Resource.from_contents without constructing a resource (i.e. it simply returns the detected specification).

v0.31.1

• No user facing changes.

v0.31.0

• Add referencing.jsonschema.EMPTY_REGISTRY (which simply has a convenient type annotation, but otherwise is just Registry()).

Commits

• 1863d4a Correct the return type.
• 1357a73 Handle empty pointers (root pointers) in Resource.pointer.
• a524132 Merge pull request #149 from python-jsonschema/dependabot/submodules/suite-c4...
• c0c7b72 Bump suite from 8be5a4b to c49444c
• edd1006 Merge pull request #147 from python-jsonschema/dependabot/submodules/suite-8b...
• d485584 Bump suite from 87851a6 to 8be5a4b
• 217a18d Remove a now-unneeded noqa since apparently this is fixed in new ruff.
• 2c1a8f5 Pin pyenchant to pre from below until pyenchant/pyenchant#302 is released.
• 4b51260 Make Registry.contents raise NoSuchResource when needed.
• 1782bd5 Update pre-commit hooks.
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs-gpt	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 13, 2024 9:36pm
nextra-docsgpt	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Dec 13, 2024 9:36pm

[ManishMadan2882]

@dependabot rebase

[ManishMadan2882]

jsonschema-spec 0.2.4 depends on referencing<0.31.0 and >=0.28.0

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.