← Back to issue list

[Feature request] Support proper caching when packing multi-architecture charm `craft-action/pack`

View original Github issue

Metadata

Project
craft-actions
Number
#37
Type
issue
State
open
Author
chanchiwai-ray
Labels
—
Created
Updated
Closed
—

Current evaluation

Feature request to make the pack action's cache key architecture-aware so multi-arch matrix charm builds don't collide/override each other's cache. No maintainer response, no labels, still open.

Suggested action: needs triage

Reason: The issue has zero comments, no labels and no assignee, and the issue summary confirms it is 'Untriaged, no maintainer response' — so it has never been assessed. The request is concrete: matrix.runs-on builds produce identical cache keys because architecture is not part of the key (referencing charmcraft/pack/action.yaml#L58). Note the action has since been rewritten to TypeScript/node24 (`runs: using: 'node24', main: 'dist/index.js'`), so the cited line no longer exists and the fix likely belongs in common/src, which lowers confidence that the original scope still applies.

Evaluated by: mr-cal-bot

Impact: 45 Quick Win: 20 Complexity: 25 Confidence: 68 Actionability: 60

Issue body

For building a multi-architecture charm, it is common to use `matrix.runs-on` to build multi-architecture charm in parallel. However, the cache mechanism in `craft-action/pack` does not this into account when creating the [cache key](https://github.com/canonical/craft-actions/blob/main/charmcraft/pack/action.yaml#L58), so the cache may be overridden or collided. I would like to request a support for this, thanks!

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 45
Quick Win: 20
Complexity: 25
Confidence: 68
Actionability: 60
needs triage Feature request to make the pack action's cache key architecture-aware so multi-arch matrix charm builds don't collide/override each other's cache. No maintainer response, no labels, still open.
qwen/qwen3.6-35b-a3b
Impact: 40
Quick Win: 22
Complexity: 30
Confidence: 75
Actionability: 80
needs triage Feature request to add architecture-aware cache keys to craft-action/pack for multi-arch matrix builds. Untriaged, no maintainer response.
qwen/qwen3.8-27b
Impact: 35
Quick Win: 26
Staleness: 75
Complexity: 25
Confidence: 75
Support Request: 15
needs triage Feature request to include architecture in the craft-action/pack cache key so parallel multi-arch matrix builds don't collide. Unlabelled, no maintainer response; code still uses an arch-agnostic hashfiles key, so the gap persists.
qwen/qwen3.6-35b-a3b
Staleness: 92
Complexity: 25
Confidence: 75
Support Request: 10
needs triage Feature request to fix cache key collisions in craft-action/pack when building multi-architecture charms in parallel. Untriaged, no maintainer response, inactive for over a year.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 35
Confidence: 75
Support Request: 5
needs triage Feature request to fix cache key collisions in craft-action/pack during parallel multi-architecture charm builds. Untriaged, zero maintainer interaction, inactive for over a year.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.