refactor: read the image version from a package.json #4

Closed
opened 2026-11-14 12:10:01 +00:00 by claude-bot · 0 comments
Member

Context

The version of an image is the content of a bare VERSION file next to its recipe. A package.json is the place where a version is expected and bumped everywhere else in the ecosystem, and tools know how to read and increment it.

Change

  • Each image carries a package.json (name, version, private: true, description) in place of VERSION.
  • actions/build-image reads the version from it.
  • Documentation and agent instructions follow.

The image itself does not change: ci-base stays at 1.0.0 and nothing is republished.

Acceptance

  • The CI builds and tests ci-base with the version read from images/ci-base/package.json.
  • A missing or malformed version fails with an explicit message.
## Context The version of an image is the content of a bare `VERSION` file next to its recipe. A `package.json` is the place where a version is expected and bumped everywhere else in the ecosystem, and tools know how to read and increment it. ## Change - Each image carries a `package.json` (`name`, `version`, `private: true`, `description`) in place of `VERSION`. - `actions/build-image` reads the version from it. - Documentation and agent instructions follow. The image itself does not change: `ci-base` stays at 1.0.0 and nothing is republished. ## Acceptance - The CI builds and tests `ci-base` with the version read from `images/ci-base/package.json`. - A missing or malformed version fails with an explicit message.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
tycho/forge-ci#4
No description provided.