Skip to content

chore(pins): Move hull to v0.2.0 and hull-assets to 0.1.14 - #43

Merged
ananos merged 1 commit into
mainfrom
chore/hull-0.2.0-assets-0.1.14
Nov 19, 2026
Merged

ananos merged 1 commit into
mainfrom
chore/hull-0.2.0-assets-0.1.14

Conversation

@ananos

@ananos ananos commented Nov 19, 2026

Copy link
Copy Markdown
Contributor

Moves two pins for the next release candidate (rc23), which is the bundle brig v0.6.0 is meant to install.

Details

  • hull: 4bf76a6 to d0eab08, the commit tagged v0.2.0. It still checks its urunc keys against 5c6bc70, so the urunc pin stays.
  • hull-assets: 0.1.12 to 0.1.14. The guest kernel goes from 6.18.59 to 6.18.64; urunc and urunit in the bundle are unchanged. 0.1.13 is skipped: it carries 6.18.59 too.
  • README table updated for both.

tests/source-pins.sh and tests/check-assets.sh pass locally. Not done here: a full bundle build and a boot on a host; CI builds the bundle, and I will boot rc23 on a fresh host before the tag.

BRIG_VERSION stays at v0.5.0 until brig v0.6.0 is tagged; that is a separate bump before the rc23 tag.

@ananos
ananos marked this pull request as ready for review November 19, 2026 06:37
hull d0eab08 is the commit tagged v0.2.0: it pins hvi 0.1.0-rc.3 for
macOS and still checks its urunc keys against 5c6bc70, the urunc this
bundle builds, so URUNC_REF_DEFAULT stays.

hull-assets 0.1.14 carries guest kernel 6.18.64, where 0.1.12 carries
6.18.59, with the same urunc 5c6bc70 and urunit. The bundle skips
0.1.13, which carries 6.18.59 as well.

Signed-off-by: Anastassios Nanos <ananos@nofire.ai>
@ananos
ananos force-pushed the chore/hull-0.2.0-assets-0.1.14 branch from f6fac5f to ecdeef4 Compare November 19, 2026 12:11
@ananos
ananos merged commit 8d83b8b into main Nov 19, 2026
5 checks passed
@ananos
ananos deleted the chore/hull-0.2.0-assets-0.1.14 branch November 19, 2026 12:15
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.

2 participants