Repository navigation
[meta-version-updater] Version updates - #213
platformsh-devrel wants to merge 5 commits into
Conversation
|
📋 PR Summary This automated PR bumps runtime package versions in the image registry. In the latest push, two 26.x images move up a patch (26.8.19.9 → 26.8.20.9 and 26.3.43.4 → 26.3.44.2), and the Node.js 26 image goes from 26.10.0 to 26.11.0 (NodeSource build). The other version bumps in the PR are in the same file but aren't part of this push's diff. Changes
|
![upsun-dispatch[bot]](https://avatars.githubusercontent.com/in/4153575?s=60&v=4){kind=small}
There was a problem hiding this comment.
Warning
Changes suggested — 🟡 1 warning
🔁 Incremental · 1 file reviewed
Verification
- Both clickhouse package_version updates keep normalized equal to the first three components of raw (26.8.17, 26.3.41).
- Each updated clickhouse majorMinor still matches its raw prefix (26.8 and 26.3).
- The edited JSON still parses: the registry loaded cleanly with python json.load.
No test in the diff covers this data. The backend's zod schema in backend/src/schemas/image.schema.ts checks field shapes only, so it would not catch eolFrom disagreeing with isEol or isMaintained.
Review 2 of 10 for this pull request · View the full run
| "releaseDate": "2026-08-20T00:00:00.000Z", | ||
| "eoasFrom": null, | ||
| "eolFrom": null, | ||
| "eolFrom": "2026-10-01T00:00:00.000Z", |
There was a problem hiding this comment.
🟡 Warning — Rust lifecycle status can display differently depending on which field a consumer reads.
Rust 1's upstream block now has eolFrom: "2026-10-01T00:00:00.000Z", a date that has already passed (today is 2026-10-05). The same block still says status: "supported", isMaintained: true and isEol: false. Most entries in this registry with a past eolFrom have isEol: true, isMaintained: false and status retired (for example golang 1.25 and elixir 1.15). So anything that reads isEol/isMaintained will still show this Rust version as maintained, while anything that reads eolFrom will show it as end-of-life. The registry contradicts itself about Rust's lifecycle. The updater has done this before, leaving chrome-headless 120 and elasticsearch 7.10 in the same state.
There was a problem hiding this comment.
Note
Reviewed — No new issues found · 1 still open
🔁 Incremental · 1 file reviewed
Outstanding from earlier reviews:
- 🟡 #4179861664 —
resources/image/registry.json:10518: Rust lifecycle status can display differently depending on which field a consumer reads. — Rust 1's upstream block still has eolFrom 2026-10-01 (already passed) alongside status supported, isMaintained true and isEol false.
Verification
- The 26.8 package_version bump sets raw 26.8.18.2 with normalized 26.8.18, and majorMinor 26.8 is unchanged and consistent.
- The 26.3 package_version bump sets raw 26.3.42.3 with normalized 26.3.42, and majorMinor 26.3 is unchanged and consistent.
Nothing in the diff tests this change. It is a data-only version bump in registry.json, and I did not check which CI job validates the registry.
Review 3 of 10 for this pull request · View the full run
There was a problem hiding this comment.
Note
Reviewed — No new issues found · 1 still open
🔁 Incremental · 1 file reviewed
Outstanding from earlier reviews:
- 🟡 #4179861664 —
resources/image/registry.json:10518: Rust lifecycle status can display differently depending on which field a consumer reads. — Rust 1 upstream still has eolFrom 2026-10-01, a date that has passed, while it also says status 'supported', isMaintained true and isEol false. This push did not touch that block.
Verification
- ClickHouse 26.8 raw 26.8.19.9 matches normalized 26.8.19, and majorMinor 26.8 is unchanged.
- ClickHouse 26.3 raw 26.3.43.4 matches normalized 26.3.43, and the bump stays inside the 26.3 line.
- Elasticsearch 8.19 raw and normalized both moved to 8.19.23, and majorMinor 8.19 is unchanged.
This push only bumps patch versions in three package_version blocks in registry.json, and no test in the diff covers them. I did not look for a CI schema check.
Review 4 of 10 for this pull request · View the full run
There was a problem hiding this comment.
Note
Reviewed — No new issues found · 1 still open
🔁 Incremental · 1 file reviewed
Outstanding from earlier reviews:
- 🟡 #4179861664 —
resources/image/registry.json:10518: Rust lifecycle status can display differently depending on which field a consumer reads. — Rust 1's upstream block still has eolFrom 2026-10-01 alongside status supported, isMaintained true and isEol false.
Verification
- ClickHouse 26.8 now has raw 26.8.20.9 and normalized 26.8.20, under the matching 26.8 version key.
- ClickHouse 26.3 now has raw 26.3.44.2 and normalized 26.3.44, and majorMinor 26.3 is unchanged.
- Node.js 26 bump to 26.11.0-1nodesource1 matches majorMinor 26.11 and normalized 26.11.0, and its upstream lifecycle dates are unchanged.
This auto-generated data update adds no tests. I found nothing that checks the package_version strings or keeps eolFrom consistent with isEol/status.
Review 5 of 10 for this pull request · View the full run
1 participant
This PR is auto-generated by meta-version-updater.
Summary of updates
resources/image/registry.json