Context
Base main has moved past v1.5.0 with Ubuntu/Debian apt-backed setup and dev-profile support. base-demo CI is intentionally pinned to a released Base tag, currently v1.5.0, so it should move only after Base v1.6.0 is cut.
This issue is the first slice of the Base 1.6 alignment train for base-demo.
Scope
- Wait until the
basefoundry/base v1.6.0 tag exists.
- Update
.github/workflows/tests.yml Base checkouts from v1.5.0 to v1.6.0.
- Update
tests/validate.sh release-pin guard and error text to require v1.6.0.
- Keep CI pinned to the release tag, not Base
main.
- Do not change the platform boundary wording in this issue except where required by the pin.
Validation
./tests/validate.sh
git diff --check
- GitHub Actions
validate and validate-ubuntu pass on the PR.
Dependencies
Blocked until Base v1.6.0 is tagged and available from basefoundry/base.
Follow-ups
The Ubuntu setup validation and platform-boundary documentation updates should happen in separate follow-up issues after this pin lands.
Context
Base
mainhas moved pastv1.5.0with Ubuntu/Debian apt-backed setup and dev-profile support. base-demo CI is intentionally pinned to a released Base tag, currentlyv1.5.0, so it should move only after Basev1.6.0is cut.This issue is the first slice of the Base 1.6 alignment train for base-demo.
Scope
basefoundry/basev1.6.0tag exists..github/workflows/tests.ymlBase checkouts fromv1.5.0tov1.6.0.tests/validate.shrelease-pin guard and error text to requirev1.6.0.main.Validation
./tests/validate.shgit diff --checkvalidateandvalidate-ubuntupass on the PR.Dependencies
Blocked until Base
v1.6.0is tagged and available frombasefoundry/base.Follow-ups
The Ubuntu setup validation and platform-boundary documentation updates should happen in separate follow-up issues after this pin lands.