Bump deps and add CI #396
Open
Bump deps and add CI #396
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: James Calligeros <[email protected]>
Signed-off-by: James Calligeros <[email protected]>
Signed-off-by: James Calligeros <[email protected]>
Member
Author
|
Ignore the PackIt failures, this can't even run on Linux... |
Member
|
The PackIt failures are because we need to bump deps on the Fedora side as well whenever they're updated in |
Member
|
This lgtm. Please also add something to the README to document how the new release pipeline works for future reference. |
davide125
approved these changes
Oct 26, 2025
Member
Author
|
Line-wrapped readme so that it's editable by a human in a text editor and added a couple of sentences about where the latest installer will come from when/if this is merged |
Conan-Kudo
approved these changes
Nov 7, 2025
davide125
approved these changes
Nov 7, 2025
jannau
approved these changes
Nov 8, 2025
Member
jannau
left a comment
jannau
left a comment
There was a problem hiding this comment.
ok with me. I left a few comments to simplify the CI workflows
Signed-off-by: James Calligeros <[email protected]>
This reusable workflow builds the installer then uploads the artefact to the correct endpoint. It is designed to be wrapped and called by workflows with the correct triggers and endpoint specified as an input. Signed-off-by: James Calligeros <[email protected]>
This workflow runs on every tagged release and uploads the build to the CDN as the latest production version Signed-off-by: James Calligeros <[email protected]>
Builds on every push to main and uploads the artefact to the CDN for use as the latest dev installer Signed-off-by: James Calligeros <[email protected]>
Signed-off-by: James Calligeros <[email protected]>
Signed-off-by: James Calligeros <[email protected]>
Signed-off-by: James Calligeros <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Been a while since we updated the deps, and while doing so noticed that the release procedure is basically that one Honda Odyssey ad.
Bump the runtime dependencies and tethered m1n1 version, and add some CI pipelines so that manual handling for releases is reduced. If we decide to go down this path, we should then move the bootstrap scripts into the installer data repo so that they can be updated without manual branch handling.