Repository navigation
feat: Release 0.9.3.1 (Multi-Arch, AARCH64, Secure CI) - #1
Merged
Merged
Conversation
… and update release workflow for artifact consumption.
Vladush
force-pushed
the
feat/secure-release-workflow
branch
from
January 3, 2026 10:46
ceeed2b to
7d69faa
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
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.
Overview
This PR migrates Debian packaging to the CI workflow, enabling multi-arch support and securing the release process.
Key Changes
arm64->aarch64across Dockerfiles and CI/CD pipelines.ci.ymlnow builds and extracts.debpackages foramd64(implied via native runner/cmake cpack if active or future),aarch64,i386, andriscv64.release.ymlis now dependent on successful CI runs and consumes artifacts directly, stripping the need for a separate build step in release..cachefrom git tracking and added to.gitignore.0.9.3.1.Verification
ctest.