chore(deps): bump tinyland-inc/ci-templates/.github/workflows/js-bazel-package.yml from 61cd1338ca9dae8a25985c0a36ff7beb111449be to d321dbd8da913e3b1bf44b0c42566e9af3a1631d

[dependabot]

Bumps tinyland-inc/ci-templates/.github/workflows/js-bazel-package.yml from 61cd1338ca9dae8a25985c0a36ff7beb111449be to d321dbd8da913e3b1bf44b0c42566e9af3a1631d.

Changelog

Sourced from tinyland-inc/ci-templates/.github/workflows/js-bazel-package.yml's changelog.

Changelog

Format: Keep a Changelog. Versioning: SemVer 2.0.

[Unreleased]

Fixed

• repo-manifest-validate routes by schema_version instead of hardcoding v1 (MINOR — a previously-failing consumer starts passing; no passing consumer changes). The composite passed schemas/tinyland-repo-manifest.schema.json unconditionally, so a spoke that had migrated to the published schema_version 2 failed the gate with a wall of Additional properties are not allowed ending in at /schema_version: 1 was expected — the gate blaming the manifest for declaring the version it actually declares, when the real fact was that the action had no branch for it. schemas/tinyland-repo-manifest.v2.schema.json is now vendored alongside v1, and the action passes --schemas-dir schemas so scripts/manifest-schema-validate.py owns the whole version → schema mapping in one place (SCHEMA_BY_VERSION). Routing is total: an absent, mistyped, or unpublished version exits 3 naming the value it saw, never silently routed to v1; a version that routes to a schema missing from the ci-templates checkout exits 4, because that means nothing validated the manifest at all. validate-ci-templates.py cache-backed-optin-contract now fails if the action resolves a schema file itself or if a mapped version is not vendored here.

• The router and the schema it routes to now agree about what an integer is. schema_version: 2.0 exited 3 as "mistyped" while the v2 schema it would have routed to accepts 2.0 outright — JSON Schema 2020-12 counts a number with zero fractional part as an integer and compares numbers mathematically, so the gate was rejecting a document that is in fact conformant and telling the operator to fix it. _as_schema_version() now accepts integral floats and still rejects true (bool subclasses int in Python, but true is not version 1 in JSON), 2.5, NaN, and inf.

• The fallback validator compared const/enum with Python equality, so a JSON boolean satisfied a numeric const. True == 1 in Python; in JSON a boolean and a number are never equal. Pointed at the v1 schema, whose schema_version is {"const": 1}, the subset returned exit 0 for {"schema_version": true} where the authoritative validator returns 1 — measured against the previous revision of the file. Comparison is now _json_equal(), implementing the 2020-12 equality rules; note this is not a type check, because numbers must still compare mathematically (1.0 satisfies {"const": 1}), and the harness pins both directions.

• The dependency-free fallback validator no longer under-enforces the schema it is pointed at. Its JSON Schema subset implemented neither not, anyOf, nor contains — which is how the v2 schema expresses every boundary rule (17/4/13 occurrences: a spoke must NOT claim apply-plane authority, a layered

... (truncated)

Commits

• d321dbd Merge pull request #146 from tinyland-inc/fix/manifest-validate-v2-dispatch
• b653941 fix(repo-manifest-validate): compare JSON values by JSON's rules, and make th...
• 6f48ef0 fix(repo-manifest-validate): route the manifest by schema_version instead of ...
• 4a31f34 Merge pull request #144 from tinyland-inc/chore/repo-json-gitops-receiver-ret...
• 793deaa chore(manifest): retire the stale gitops-receiver assertions (PATCH)
• d8d178c Merge pull request #143 from tinyland-inc/feature/v3.1.0-release-20260819
• 24e134b release: v3.1.0
• 28d6777 Merge pull request #142 from tinyland-inc/feat/tin-3815-repo-role-input
• 00e64ce fix(ci): name TIN-3914 as the internal-ref debt ledger owner (TIN-3815 review)
• afc2220 fix(spoke-ci): normalize allowed_repo_roles in the workflow; unfreeze the v2-...
• Additional commits viewable 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)

[dependabot]

Superseded by #30.