Package build workflow fix#2849
Merged
Rot127 merged 2 commits intocapstone-engine:nextfrom Feb 1, 2026
Merged
Conversation
Rot127
force-pushed
the
build-release
branch
2 times, most recently
from
dbe2fa5 to
6b99b7e
Compare
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
1 participant
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.
Your checklist for this pull request
Detailed description
Of course something had to fail during the release. In this case it was the build of the MSVC package. This fixes it by installing NSIS according to the NSIS examples.
Additionally, the workflow now runs by default and uploads the artifacts, instead of just running on release. This should prevent future issues.
Also it gives users a easy access to pre-built packages for any merged commit.
Test plan
Closing issues
...