You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
chore(build): Update snap packaging to use prebuilt binaries #1610
We want to use identical binaries across all the packaging systems, reusing same hashes, etc. We can update snapcraft.yaml to use prebuilt binaries built by earlier stages of the pipeline.
Proposed Design
We can update the snapcraft.yaml to use the dump plugin to assemble the file system of the snap from binaries that exist in the target/ directory. The CI pipeline can then reuse binaries built by earlier jobs and transfer them, as artifacts, into the job that calls snapcraft pack
Alternatives Considered
Making identical builds (reproducible builds) is possible but would not avoid cost of building on every merge.
Agent Investigation
No response
Checklist
I've reviewed existing issues and the architecture docs
This is a design proposal, not a "please build this" request
changed the title [-]Update snap packaging to use prebuilt binaries[/-][+]chore(build): Update snap packaging to use prebuilt binaries[/+]on Jun 2, 2026
This issue has had no activity for 14 days and is now marked stale. It may be closed in 7 days if there is no further activity. Comment or remove the state:stale label to keep it open.
Hi @zyga 🙂! from reviewing parent issue CI/CD & Testing Improvements, this is marked as Todo, but IIUC this issue was resolved by #1651... can this be marked as closed&done? (same for issue #1611)
This issue has had no activity for 14 days and is now marked stale. It may be closed in 7 days if there is no further activity. Comment or remove the state:stale label to keep it open.
Activity
[-]Update snap packaging to use prebuilt binaries[/-][+]chore(build): Update snap packaging to use prebuilt binaries[/+]github-actions commentedon Jun 17, 2026
This issue has had no activity for 14 days and is now marked stale. It may be closed in 7 days if there is no further activity. Comment or remove the state:stale label to keep it open.
eviehoward commentedon Aug 20, 2026
Hi @zyga 🙂! from reviewing parent issue CI/CD & Testing Improvements, this is marked as
Todo, but IIUC this issue was resolved by #1651... can this be marked as closed&done? (same for issue #1611)github-actions commentedon Sep 12, 2026
This issue has had no activity for 14 days and is now marked stale. It may be closed in 7 days if there is no further activity. Comment or remove the state:stale label to keep it open.