Skip to content

chore(hydra-gates): vendor manifest schema 2.49.0 - #826

Merged
rubenvdlinde merged 1 commit into
mainfrom
chore/vendored-manifest-schema-2.49.0
Oct 7, 2026
Merged

rubenvdlinde merged 1 commit into
mainfrom
chore/vendored-manifest-schema-2.49.0

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 7, 2026

Copy link
Copy Markdown
Contributor

The vendored manifest schema was at 2.47.0. @conduction/nextcloud-vue 2.67.0 ships 2.49.0.

Gates 22 and 53 validate every app's manifest against the vendored copy, so until this merges an app that adopts a key 2.49.0 added is rejected by the gate while its own npm run check:manifest passes.

Before merging

CI resolves these gates at @main, so this reaches all 21 swept apps the minute it lands. Constraints that got stricter in this diff:

none

none means the diff is additive and cannot redden a manifest that passes today. Anything else means it can, and the fleet's effective manifests need validating against both schemas first.

Opened by .github/workflows/hydra-gates-schema-sync.yml. See #785 for why the vendored copy needs a keeper.

@rubenvdlinde
rubenvdlinde merged commit 628b33c into main Oct 7, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant