← Back to issue list

Add published date column to `charmcraft statsus` output

View original Github issue

Metadata

Project
charmcraft
Number
#1998
Type
issue
State
open
Author
taurus-forever
Labels
Created
Updated
Closed

Current evaluation

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.

Suggested action: keep open

Reason: Maintainer @lengau acknowledged on 2024-11-18 that it is 'pretty straightforward' and identified the exact fix (add the 'when' field from the store response). A Jira ticket (CRAFT-3699) was created, confirming triage. Code inspection confirms the Release dataclass in charmcraft/store/models.py still lacks a 'when' field and list_releases in charmcraft/store/store.py does not parse it, so the feature remains unimplemented and the issue is still relevant despite ~12 months of inactivity.

Impact: 30 Quick Win: 24.0 Staleness: 65 Complexity: 20 Confidence: 80 Support Request: 10

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.: ![image](https://github.com/user-attachments/assets/a407b1b9-5ebf-4f96-b6cc-e58453bfc786) 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
qwen/qwen3.8-27b
Impact: 30
Quick Win: 24.0
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.
qwen3.6-35b-a3b-mtp-q6
Staleness: 75
Complexity: 20
Confidence: 85
Support Request: 0
keep open Add published date column to charmcraft status output for better revision tracking. Implementation is straightforward, requiring only the API when field. Open with internal ticket created, awaiting implementation. Last activity 304 days ago.

Update history

No update history recorded yet.

Related work

  • Related To: charmcraft#1997 (confidence 75%)

    Referenced in the issue body as a related use case: identifying no longer supported/published bases would be aided by having published dates visible in status output.

Related issues

No related issues found above the similarity threshold.