Skip to content

Conversation

@pietroalbini
Copy link
Member

This PR updates Brussels to 0.2.0 (oxidecomputer/brussels#7) and makes the necessary changes to be compatible with it.

This release of Brussels doesn't change the manual steps needed to publish a release (it still only does the tagging and initial build), and instead contains these changes:

  • Records the commit we are releasing in the manifest, so that the rest of the (future) release process will be able to rely on it.
  • Rather than hardcoding the release groups in the Brussels source code, there is now a file in the Hubris repository, brussels.toml. The fine defines both how to create the tag and the list of boards to release.

Along with the update I changed the GitHub release creation code to use the commit we are actually releasing, instead of releasing the latest commit on main unconditionally. This will prevent cases like the all-sp-v1.0.49 tag pointing to the wrong commit.

@pietroalbini pietroalbini requested a review from labbott November 24, 2025 11:49
@pietroalbini pietroalbini force-pushed the ea-brussels-020 branch 2 times, most recently from 7583fa2 to 34b8f37 Compare November 25, 2025 10:54
@pietroalbini pietroalbini enabled auto-merge (squash) November 25, 2025 15:04
@pietroalbini pietroalbini merged commit e0f4bad into master Nov 25, 2025
165 checks passed
@pietroalbini pietroalbini deleted the ea-brussels-020 branch November 25, 2025 15:13
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.

3 participants