chore(deps): bump Astro stack to 7.1.6 / @astrojs/node 11.0.3 - #365
Conversation
Replaces #354 and #355, which are closed. Dependabot raises them separately; they land as one change because `awcms-family-compatibility.yaml` pins BOTH in its `stack` block, and `family:conformance:check` fails on any drift between a declared range and `package.json`. So each bump alone reddens CI until its `declared` value moves with it — which is exactly what #354 and #355 show (`[FAIL] stack: Astro (declared ^7.1.3 vs actual ^7.1.6)`). That gate is why the versions a consumer reads have never silently diverged from the versions this repo runs, so the fix is to move the manifest with the bump, not to loosen the check. Verified: `bun install --frozen-lockfile` clean, the CI-equivalent `quality` suite green (3040 pass / 0 fail, DB-gated tests skipped as in CI), lint, docs, contracts, conformance, typecheck and build all pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://cdn.github.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 015d1e5be5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "dependencies": { | ||
| "@astrojs/node": "^11.0.2", | ||
| "astro": "^7.1.3" | ||
| "@astrojs/node": "^11.0.3", |
There was a problem hiding this comment.
After this bump, docs/awcms/family-compatibility.md:55 still identifies ^11.0.2 as both the current and minimum-supported @astrojs/node version, despite naming this dependency as its source. Anyone using the compatibility matrix now receives a contract that conflicts with package.json and the manifest; update that row to ^11.0.3 alongside the dependency change.
AGENTS.md reference: AGENTS.md:L77-L77
Useful? React with 👍 / 👎.
1 participant
Menggantikan #354 dan #355, keduanya ditutup.
Kenapa digabung
Dependabot menaikkannya sebagai dua PR. Keduanya mendarat sebagai satu perubahan karena
awcms-family-compatibility.yamlmem-pin keduanya di blokstack, danfamily:conformance:checkgagal pada tiap selisih antara rentang ter-deklarasi danpackage.json:Itu yang memerahkan
QualitydanMinimum-supported versionsdi #354 dan #355 — jadi tiap bump sendirian memerahkan CI sampai nilaideclared-nya ikut bergerak.Gerbang itu justru alasan versi yang dibaca konsumen tak pernah diam-diam menyimpang dari versi yang benar-benar dijalankan repo ini. Perbaikannya menggerakkan manifest bersama bump-nya, bukan melonggarkan cek.
Verifikasi
bun install --frozen-lockfilebersih (336 installs, no changes)qualityCI (DB-gated di-skip persis seperti CI): 0 fail, 457 skiplint,check:docs,api:spec:check,api:docs:check,family:conformance:check(23/23),modules:compose:check,typecheck,build— semua hijau🤖 Generated with Claude Code