Add published date column to `charmcraft statsus` output
Metadata
Current evaluation
Maintainer-acknowledged feature to show Charmhub's per-channel "when" value as a Published column in charmcraft status; current code still discards that field.
Suggested action: keep open
Reason: Maintainer @lengau called this straightforward and identified the store response's "when" field as the needed data. StatusCommand still has no Published header, while Store.list_releases parses channel-map entries without "when", despite existing API fixtures containing it, so the feature remains valid and ready to implement.
Evaluated by: mr-cal-bot
Impact:
40
Quick Win:
25
Complexity:
28
Confidence:
95
Actionability:
88
Issue body
### What needs to get done
Hi,
Sometimes it is necessary to know the specific revision release date.
At the moment it is visible on the charmhub WEB only, e.g.:
It would be nice to have the same information in `charmcraft status` table:
```
> charmcraft status data-platform-libs
Track Base Channel Version Revision Published
latest ubuntu 20.04 (amd64) stable 2 2 21 Jul 2022
candidate ↑ ↑
beta ↑ ↑
edge 9 9 21 OCt 2022
ubuntu 22.04 (amd64) stable 54 54 01 Nov 2023
candidate 81 81 15 Nov 2023
beta ↑ ↑
edge 81 81 27 Sep 2024
```
### Why it needs to get done
For better navigation in the `juju status` output during the manual promotion of the new revisions.
Will improve community charms/charmcraft/charmhub usability.
It will also help to identify no longer supported/published bases: https://github.com/canonical/charmcraft/issues/1997
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
40
Quick Win:
25
Complexity:
28
Confidence:
95
Actionability:
88
|
keep open | Maintainer-acknowledged feature to show Charmhub's per-channel "when" value as a Published column in charmcraft status; current code still discards that field. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
17
Complexity:
20
Confidence:
70
Actionability:
70
|
keep open | Feature request to add a published date column to `charmcraft status` output using the `when` field from the store API. Maintainer confirmed it's straightforward. | |
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
24
Staleness:
65
Complexity:
20
Confidence:
80
Support Request:
10
|
keep open | Feature request to add a Published date column to charmcraft status output, showing when each revision was released. Maintainer acknowledged it as straightforward (add the 'when' field from store API), Jira ticket CRAFT-3699 created, but no implementation progress in ~12 months. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
65
Complexity:
15
Confidence:
80
Support Request:
10
|
keep open | Feature request to add a published date column to the charmcraft status CLI output. Acknowledged as straightforward by a maintainer but remains unassigned and inactive for over a year. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
75
Complexity:
20
Confidence:
70
Support Request:
10
|
keep open | Feature request to add a published date column to the charmcraft status CLI output for better revision tracking. Maintainer acknowledged it as straightforward, but it has been inactive for over 10 months with no labels or assignee. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
75
Complexity:
20
Confidence:
90
Support Request:
10
|
needs triage | Feature request to add a published date column to the charmcraft status CLI output. Currently unlabelled and inactive for over ten months, though a maintainer noted it is straightforward to implement by adding the store API when field. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/charmcraft#1997
(confidence 95%)
The reporter says the new column would help identify no longer supported or published bases, which is the concern tracked by #1997.
Related issues
No related issues found above the similarity threshold.