Repository navigation
ci: add the release workflow to main so it can be dispatched against develop commits - #255
Merged
Merged
Conversation
This was referenced Oct 6, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why. GitHub can start a manual workflow only from the default branch (
main).release-package.yml(#241, #247) exists only ondevelop, so the alpha.7 and alpha.8 test releases for Mac, Linux x86-64 and Jetson cannot be built.Change. This adds exactly that one file, byte-identical to
developat6a4f17dc. Nothing else onmainchanges.What the workflow does.
workflow_dispatch) with a source commit. It refuses any commit that is not ondevelopor the head of an open PR intodevelop.Undo. Delete the file.
Decision: Anders, 6 Oct ("yes please").