ci: bump berntpopp/genefoundry-router/.github/workflows/_container-ci.yml from 0.8.5 to 0.8.7

[dependabot]

Bumps berntpopp/genefoundry-router/.github/workflows/_container-ci.yml from 0.8.5 to 0.8.7.

Release notes

Sourced from berntpopp/genefoundry-router/.github/workflows/_container-ci.yml's releases.

v0.8.7

Verified GeneFoundry research-use-only container release.

v0.8.6

Verified GeneFoundry research-use-only container release.

Changelog

Sourced from berntpopp/genefoundry-router/.github/workflows/_container-ci.yml's changelog.

Changelog

All notable changes to genefoundry-router are documented here.

[0.9.0] - 2026-09-06

Added

• Added clinpgx-link backend (pharmacogenomics: CPIC, PharmGKB, PharmCAT) as the 22nd backend in servers.yaml.
• Added canonical fleet provenance endpoints (GET /provenance and GET /api/fleet/provenance) serving verified database and release provenance for all 22 backends and 285 tools.
• Generated ci/fleet-provenance.json and bundled genefoundry_router/data/fleet-provenance.json.
• Added generator script scripts/gen_fleet_provenance.py and unit tests in tests/unit/test_provenance.py.

[0.8.7] - 2026-09-02

Changed

• Regenerated the fleet release-evidence set (ci/fleet-application-releases.json, ci/release-candidate-inventory.json, genefoundry_router/data/fleet-baseline.json, ci/release-candidate-fleet.json) at identity fleet-2026-09-02-contract-remediation, captured against the live fleet (all 21 -link backends on their current releases) after the controller contract-remediation deploy/activation campaign. Closes #170.

[0.8.6] - 2026-09-02

Added

• Release configuration: optional data.schema_compatibility in container-release.json — the data schema versions the application can serve, declared in every data mode as fleet identifiers ("4", "5.1", "schema-6"). The release workflow already projected the field into the published manifest, but ReleaseConfig's data models forbid extra keys, so a repository that declared it failed validate-config with "Extra inputs are not permitted" and every data-bearing manifest in the fleet published "schema_compatibility": []. The fleet controller's data attestation requires the attested schema version to be a member of that list and refuses an empty one, so no data release could be activated. Omitting the field still publishes []; existing repositories are unaffected. Documented under "data.schema_compatibility" in docs/deployment.md.

Changed

• data_requirements.schema_compatibility in the application release manifest is now validated as a bounded list of fleet identifiers rather than free-form strings, so a range expression that no consumer evaluates can no longer be published as if it were a version.

[0.8.5] - 2026-09-02

Added

• Release: gate the deployed Compose overlay (docker/docker-compose.npm.yml) centrally, in the shared reusable release workflow, so every fleet repository inherits the same deploy

... (truncated)

Commits

• 6568a0a chore(release): bump version to 0.8.7 (#175)
• 3a43cc3 deploy: re-pin the drift baseline to fleet-2026-09-02-contract-remediation (#...
• 3d3cc20 feat(release): let a backend declare the data schema versions it serves (#173)
• See full diff in compare view

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @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)