[Feature Request] Add `name`, `version`, `arch` and any other useful metadata as outputs of `rockcraft-pack-action`

Metadata

Project: craft-actions
Number: #20
Type: issue
State: open
Author: ca-scribner
Labels: —
Created: 2023-12-06 07:22 PM UTC
Updated: 2023-12-06 07:22 PM UTC
Closed: —

Current evaluation

Feature request (open, no labels, no comments since ~1030 days) to expose name, version, arch and other rock metadata as outputs of the rockcraft-pack action, alongside the existing rocks output, to ease CI chaining with skopeo copy.

Suggested action: needs triage

Reason: The issue has zero labels, zero comments, no assignee and no maintainer response, so it has never been triaged — the default action for unlabelled new requests. It is still not implemented: rockcraft/pack/action.yaml declares only `rocks`, `rockcraft-revision` and `lxd-revision` outputs, no name/version/arch metadata, so it is a valid, still-open feature request rather than resolved or stale. It is somewhat underspecified (`any other useful metadata`, `probably others` is open-ended, and the exact output names/shape — e.g. separate outputs vs. a JSON blob — are undecided), and Rockcraft's own metadata surface may have shifted in ~3 years, so scope needs maintainer input before implementation.

Evaluated by: mr-cal-bot

Impact: 40 Quick Win: 10 Complexity: 45 Confidence: 55 Actionability: 45

Issue body

The `rockcraft-pack-action` provides an output `rock` (the filename of the rock produced). This is great for CI as reduces the boilerplate code needed to consume the output. For the same reason, it would be great if this action also provided data like `name`, `version`, and probably others. This would make it really easy to chain a `rockcraft-pack` call with a `skopeo copy`, etc. A use can currently inspect the `rockcraft.yaml` file to get this information, but it feels more natural and convenient to be provided these directly from `rockcraft-pack-action`

Evaluation history

Date	Model	Scores	Action	Summary
2026-10-02 05:57 PM UTC	stealth/space-bunny-alpha	Impact: 40 Quick Win: 10 Complexity: 45 Confidence: 55 Actionability: 45	needs triage	Feature request (open, no labels, no comments since ~1030 days) to expose name, version, arch and other rock metadata as outputs of the rockcraft-pack action, alongside the existing rocks output, to ease CI chaining with skopeo copy.
2026-09-21 08:01 PM UTC	qwen/qwen3.6-35b-a3b	Impact: 30 Quick Win: 17 Complexity: 30 Confidence: 70 Actionability: 80	needs triage	Feature request to add name, version, arch, and other metadata as outputs of the rockcraft-pack-action GitHub Action alongside the existing rock filename output.
2026-09-01 04:59 AM UTC	qwen/qwen3.8-27b	Impact: 35 Quick Win: 23 Staleness: 88 Complexity: 35 Confidence: 70 Support Request: 10	needs triage	Feature request to expose name, version, arch and other metadata as outputs of rockcraft-pack-action for easier CI chaining (e.g. skopeo copy). Unlabelled, no maintainer response, ~999 days old; still unimplemented (action only outputs rock and revisions).
2026-07-22 01:21 PM UTC	qwen/qwen3.6-35b-a3b	Staleness: 95 Complexity: 20 Confidence: 85 Support Request: 10	close stale	Feature request to expose rock metadata as GitHub Action outputs for easier CI chaining. Unanswered and inactive for over two years.
2026-07-09 04:22 AM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 95 Complexity: 20 Confidence: 85 Support Request: 10	close stale	Feature request to expose build metadata as outputs for the rockcraft-pack-action. Unlabeled, no maintainer response, inactive for over two years.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.