update-twoliter

To update Bottlerocket repos to a new Twoliter version, you apply the new version string and SHA256 checksums to Makefiles and Makefile.toml files across core-kit, kernel-kit, and bottlerocket. This generates consistent commits with clear messages like "chore: bump to twoliter X.Y.Z" to maintain traceability across repositories.

A Twoliter version bump involves updating TWOLITER_VERSION and TWOLITER_SHA256 values in each kit's Makefile and in bottlerocket/Makefile.toml. It automates applying these changes across core-kit, kernel-kit, and related tooling to ensure consistency and reduce manual errors during the release cycle.

You automate SHA256 checksum updates for Twoliter by applying the new Twoliter version and corresponding checksums directly into the Makefile and Makefile.toml configurations. This updates all kits and the bottlerocket repo simultaneously, creating reproducible commits for each changed repository.

Yes, you can use this to bump Twoliter versions across core-kit and kernel-kit simultaneously. It applies the version bump during the Twoliter release cycle across all related Bottlerocket repositories and tooling, updating the necessary Makefiles and creating commits in one bulk workflow.

The best way to ensure consistent commits when bumping Bottlerocket dependencies is to automate the version bump process. This generates clear, reproducible commit messages across multiple repositories, ensuring consistency and traceability while avoiding the errors associated with manual updates.