Skip to content

chore: catalogue new Splice versions - #353

Merged
zheli merged 1 commit into
mainfrom
chore/refresh-splice-versions
Oct 12, 2026
Merged

zheli merged 1 commit into
mainfrom
chore/refresh-splice-versions

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

Auto-generated by .github/workflows/refresh-versions.yml.

New Splice tags added to internal/splice/versions.json:

0.9.0

Each entry was added by scripts/add-splice-version.sh, which:

  1. Resolves the tag → commit SHA via the GitHub REST API
    (peeling annotated tags).
  2. Downloads the source archive at that commit.
  3. Computes the deterministic ContentSHA of the extracted
    cluster/compose/localnet/ subtree.

Reviewer checklist:

  • Confirm each new tag corresponds to a release we want
    to support (not a pre-release artifact).
  • Bump latest_alias in versions.json if the newest
    catalogued tag should be the default latest.
  • Consider scheduling an integration run against the
    newest entry before merging.

@zheli
zheli merged commit d934472 into main Oct 12, 2026
1 check passed
@zheli
zheli deleted the chore/refresh-splice-versions branch October 12, 2026 14:28
srikanth-bitdynamics added a commit that referenced this pull request Oct 22, 2026
#353 catalogued 0.9.0 without min/recommended memory. It is the only 0.9
entry, so there was no same-major floor to inherit: the pre-flight gate
fell back to the 4 GiB default and the low-memory warning was disabled
(RecommendedMemoryFor = 0). TestSpliceMemoryFloors_NeverBelowDockerGate
has been failing on main since.

Upstream 0.9.0's LocalNet resource-constraints.yaml is identical to
0.8.1's (13 limits, 13.16 GiB total), so use the same 8 GB / 12 GB
floors. Add a catalogue test so a newly catalogued major cannot ship
without a curated floor again.
zheli pushed a commit that referenced this pull request Oct 22, 2026
…logue changes (#363)

* fix(splice): curate memory floors for Splice 0.9.0

#353 catalogued 0.9.0 without min/recommended memory. It is the only 0.9
entry, so there was no same-major floor to inherit: the pre-flight gate
fell back to the 4 GiB default and the low-memory warning was disabled
(RecommendedMemoryFor = 0). TestSpliceMemoryFloors_NeverBelowDockerGate
has been failing on main since.

Upstream 0.9.0's LocalNet resource-constraints.yaml is identical to
0.8.1's (13 limits, 13.16 GiB total), so use the same 8 GB / 12 GB
floors. Add a catalogue test so a newly catalogued major cannot ship
without a curated floor again.

* ci: run Go tests when embedded catalogue or assets change

CI's path filters only matched Go, frontend and a few doc trees, so the
refresh-versions bot PR #353 (versions.json only) ran no Go tests and
merged with TestSpliceMemoryFloors_NeverBelowDockerGate failing; the
push to main skipped CI for the same reason. versions.json, assets/ and
internal/ui/dist/ are all //go:embed inputs to the Go suite, so add them
to both the pull_request and push filters.

Document that the first entry of a new Splice major needs curated
memory floors, which TestEveryCataloguedMajorHasCuratedFloor enforces.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant