CommunityProgramación y desarrollogithub.com

update-twoliter

Update all Bottlerocket repositories to a new Twoliter version

Compatible con~Claude Code~Codex CLI~Cursor
npx add-skill https://github.com/cbgbt/bottlerocket-forest/tree/main/skills/update-twoliter

name: update-twoliter description: Update all Bottlerocket repositories to a new Twoliter version

Skill: Update Twoliter Version

Purpose

Update all repositories in the forest to a new version of Twoliter. This creates git commits in core-kit, kernel-kit, and bottlerocket repositories with the updated version and SHA256 checksums.

When to Use

  • Testing a new Twoliter release candidate
  • Updating to a new stable Twoliter release
  • Preparing pull requests to trigger CI testing with a new Twoliter version

Prerequisites

  • All repositories cloned in the forest
  • Git configured with author information
  • Network access to GitHub releases

Procedure

1. Fetch SHA256 checksums for the new version

Replace X.Y.Z with the target version (e.g., 0.13.0 or 0.13.0-rc1):

# For x86_64
curl -sSL "https://github.com/bottlerocket-os/twoliter/releases/download/vX.Y.Z/twoliter-x86_64-unknown-linux-musl.tar.xz.sha256"

# For aarch64
curl -sSL "https://github.com/bottlerocket-os/twoliter/releases/download/vX.Y.Z/twoliter-aarch64-unknown-linux-musl.tar.xz.sha256"

2. Update all kits

For each kit in the worktree (e.g., bottlerocket-core-kit, bottlerocket-kernel-kit), edit the Makefile:

TWOLITER_VERSION ?= "X.Y.Z"
TWOLITER_SHA256_AARCH64 ?= "<aarch64-sha256>"
TWOLITER_SHA256_X86_64 ?= "<x86_64-sha256>"

Commit each kit:

cd kits/<kit-name>
git add Makefile
git commit -m "chore: bump to twoliter X.Y.Z"
cd ../..

3. Update bottlerocket

Edit bottlerocket/Makefile.toml in the worktree (note the v prefix):

TWOLITER_VERSION = "vX.Y.Z"
TWOLITER_SHA256_AARCH64 = "<aarch64-sha256>"
TWOLITER_SHA256_X86_64 = "<x86_64-sha256>"

Commit:

cd bottlerocket
git add Makefile.toml
git commit -m "chore: bump to twoliter X.Y.Z"

Validation

Verify commits were created in all kits and bottlerocket:

# Check each kit
for kit in kits/*/; do
  echo "=== $(basename $kit) ==="
  (cd "$kit" && git show HEAD --stat)
done

# Check bottlerocket
(cd bottlerocket && git show HEAD --stat)

Each should show:

  • Commit message: chore: bump to twoliter X.Y.Z
  • 1 file changed, 3 insertions(+), 3 deletions(-)

Common Issues

SHA256 checksum not found:

  • Verify the release exists: https://github.com/bottlerocket-os/twoliter/releases/tag/vX.Y.Z
  • Check that binary artifacts are attached to the release

Wrong version format:

  • Kits use "X.Y.Z" (no v prefix) in their Makefiles
  • bottlerocket uses "vX.Y.Z" (with v prefix) in Makefile.toml

Amending commits: If you need to update an existing commit (e.g., moving from RC to stable):

# Make the file changes, then:
git add <file>
git commit --amend -m "chore: bump to twoliter X.Y.Z"

Related Skills

  • None (standalone skill)

Notes

  • This skill does NOT push commits or create pull requests
  • After creating commits, you can push them and create PRs manually
  • PRs will trigger CI to test the new Twoliter version
  • Schema version changes are rare; only update if release notes specify

Individual skills in this repo

This repo contains 19 individual skills — each has its own dedicated page.

ad-hoc-implementation-plan

Transform a rough plan into implement-commit ready artifacts. Allows rigorous review while implementing.

build-kit-locally

Build a kit and publish it to a locally hosted registry for development testing

build-variant-from-local-kits

Build a variant using locally published kits for development validation

deep-research

Create educational documents that build understanding progressively with citations

edit-spec-file

Edit Bottlerocket RPM spec files following project style conventions

fact-find

Quick lookup of specific facts about Bottlerocket with citations

idea-honing

Clarify feature ideas through iterative Q&A, recording insights to guide concept development

implement-commit

Implement commits from an implementation plan using a TDD pipeline

local-registry

Start and manage a local OCI registry for Bottlerocket kit development

prepare-core-kit-release

Prepare bottlerocket-core-kit for release by bumping version and updating changelog

propose-feature-concept

Create a new feature concept document to pitch the idea and explain the problem/solution

propose-feature-design

Create or update feature technical design document with architecture and implementation guidance

propose-feature-requirements

Create or update feature requirements specification using EARS notation with examples and appendices

propose-feature-test-plan

Create a test plan mapping EARS requirements and Critical Constraints to specific tests

propose-implementation-plan

Create an implementation plan with atomic commits that build toward a complete feature

review-code

Deep code review generating PR comments via principled question-driven analysis

review-scope

Verify code changes match intended scope and requirements without exceeding boundaries

review-style

Verify code follows project style guides without providing improvement suggestions

test-local-twoliter

Build and test local changes to twoliter before releasing

Skills relacionados