build(deps): bump redis from 0.28.2 to 0.29.0#2531
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [redis](https://github.com/redis-rs/redis-rs) from 0.28.2 to 0.29.0. - [Release notes](https://github.com/redis-rs/redis-rs/releases) - [Commits](redis-rs/redis-rs@redis-0.28.2...redis-0.29.0) --- updated-dependencies: - dependency-name: redis dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Contributor
Author
|
Looks like redis is up-to-date now, so this is no longer needed. |
9 tasks
jqnatividad
added a commit
that referenced
this pull request
May 27, 2026
…3914) * feat(profile): geoconnex projection profile + pyshacl SHACL validator (feature-gated) Phase 1 dataset-level projection emitting Geoconnex hydrologic linked-data JSON-LD (https://docs.geoconnex.us/) wired to pyshacl against the vendored upstream SHACL shapes (~10KB Turtle bundle from internetofwater/nabu, commit e5d6ad39, Apache-2.0). Covers DatasetShape / ProviderShape / PublisherShape / DistributionShape; the row-per-feature LocationOrientedShape (mandatory gsp:asWKT geometry synthesis from lat/lon columns) is deferred to a follow-up that introduces a `for_each_row` projection mode. Gated behind a new `geoconnex` cargo feature so the embedded SHACL bytes don't ship in qsvlite / qsvmcp / qsvdp-default builds. Included in qsv via distrib_features; qsvdp can opt in with `-F datapusher_plus,geoconnex`. Without the feature, --profile geoconnex falls through to load()'s existing "unknown profile" error path listing the bundled names. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(profile): roborev #2531 — profile-aware catalog keys + publisher fallback Medium (geoconnex.yaml:266): the catalog envelope wrapper hard-coded `dct:title` and `dcat:dataset`, which broke the JSON-LD envelope for profiles whose @context doesn't declare those prefixes (schema.org- rooted Geoconnex). Add `title_key` (default `dct:title`) and `dataset_key` (default `dcat:dataset`) to CatalogBlock so the wrapper honours profile-specific keys; thread them through wrap_as_catalog and legacy_catalog_title. Geoconnex now pins schema:name + schema:dataset (the canonical schema.org DataCatalog → Dataset relation). DCAT-US/DCAT-AP defaults preserved. Low (geoconnex.yaml:177): schema:publisher fallback used `pkg.maintainer | default(pkg.publisher | default(""))` which doesn't re-fall-through when `maintainer` is defined-but-empty (common CKAN shape). Switched to `pkg.maintainer or pkg.publisher or ""` matching the provider block's idiom in both template body and emit_when. Added `geoconnex_catalog_uses_schema_org_keys_not_dcat` regression test asserting the envelope carries no dct:/dcat: keys. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * test(profile): roborev #2535 — regression test for empty-maintainer publisher fallback Low (geoconnex.yaml:179): the #2531 fix changed schema:publisher to use `pkg.maintainer or pkg.publisher or ""` but shipped without coverage. Add geoconnex_publisher_falls_through_empty_maintainer_to_publisher — uses an initial-context with maintainer="" (defined but blank, a common CKAN shape), publisher="Agency", maintainer_email set, and asserts `/dcat/schema:publisher/schema:name` resolves to "Agency". Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * build(profile): include profile YAMLs + SHACL/Schema bundles in crates.io tarball Copilot review (PR #3914): the package `include` whitelist only covered `src/**/*` plus two specific resource files, so `cargo install qsv` (any features) shipped a .crate tarball with the profile YAMLs and SHACL/Schema resources stripped out. `include_str!` at compile time would then fail on the missing files. Verified with `cargo package --list`: before this commit only README.md files leaked through; now all four profile YAMLs (dcat-us-v3, dcat-ap-v3, croissant, geoconnex), both vendored SHACL bundles, and the full DCAT-US v3 JSON Schema tree under definitions/ are included. This is a pre-existing bug that affected all four profiles equally since #3908 (DCAT-US/DCAT-AP/Croissant landed without updating the include list); fixed comprehensively rather than only patching the geoconnex paths Copilot flagged. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(features): add geoconnex to all_features + distrib_features enumerations CI's docs-drift-check flagged docs/FEATURES.md lines 30 and 36 — both the `all_features` shortcut and `distrib_features` description list their member features verbatim, and #3914 added `geoconnex` to both sets in Cargo.toml without updating the prose. Inserted `geoconnex` in alphabetical position (between `geocode` and `luau`) in both lines. Verified with `python3 scripts/docs-drift-check.py`: no drift detected. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.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
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 redis from 0.28.2 to 0.29.0.
Release notes
Sourced from redis's releases.
Commits
7ca5765Prepare v0.29.0 release (#1530)4b2377bAllow users of async connections to set TCP settings. (#1523)ffaacccRenaming tests the require the JSON module (#1527)8aee0c0Fix caching with the JSON module (#1520)745d734Allow configuring Sentinel with custom TLS certificates (#1335)0c72d64Upgrade to rand 0.9 (#1525)530269bImprove docs around TTLs/ expiry times. (#1522)ceb856dImprove pubsub docs. (#1519)ec321ecfeat: Include the reason for one connection failure if cluster connect fails ...0755090Add buffered write methods to RedisWrite (#905)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 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)