Ability to check/notify when there are library updates
Metadata
Current evaluation
Closed without implementation. A maintainer noted the feature requires network calls that could slow down packing, suggesting the lint check be ignored. The request was abandoned.
Suggested action: —
No scores available.
Issue body
If a developer is consuming a library from Charmhub, the will initially pull it in using `charmcraft fetch-lib`. Right now, the developer would need to reissue that command periodically to check for charm library updates.
Noting the [spec for charmcraft analyze](https://discourse.charmhub.io/t/proposal-charmcraft-analyze/4792), we could add a check under the `lint` category that compares those libraries imported with the latest available versions and shows the user a warning if there is a later version.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. A maintainer noted the feature requires network calls that could slow down packing, suggesting the lint check be ignored. The request was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. A maintainer noted the required network call would slow down packing, suggesting the lint warning could be ignored. The feature request was effectively abandoned due to performance concerns. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. A maintainer noted the proposed lint warning would require a network call that could slow down packing, suggesting the check be ignored instead. No implementation was pursued. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. The proposed lint warning for outdated charm libraries was deferred due to performance concerns, as the required network calls could slow down the packing process. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. Maintainer noted the proposed lint warning would require network calls that could slow down packing, suggesting it be ignored. Feature abandoned due to performance concerns. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.