Create a manifest at build time with building information
Metadata
Current evaluation
Implemented across merged PRs #279–#281; PR #281 merged into master as fe2d065f, generating manifest.yaml with build metadata during charm and bundle packaging.
Resolution: closed resolved
Reason: Build-time manifest generation was implemented in merged PRs #279–#281. PR #281, produce-manifest-2, merged via commit fe2d065f.
Evaluated by: mr-cal-bot
No scores available.
Issue body
After packing charms or bundles, we need to leave a manifest.yaml in place (and include it in the packed file) with the following fields:
- charmcraft-version: the version of the executed charmcraft
- charmcraft-started-at: timestamp in ISO format for when the packing started
- charmcraft-os-release-id: OS name
- charmcraft-os-release-version-id: OS version
- architectures: the list of archs where the charm/bundle can run on
Example:
```
charmcraft-version: 4.5.4
charmcraft-started-at: '2021-03-13T10:36:59.250861Z'
charmcraft-os-release-id: ubuntu
charmcraft-os-release-version-id: '18.04'
architectures:
- amd64
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Implemented across merged PRs #279–#281; PR #281 merged into master as fe2d065f, generating manifest.yaml with build metadata during charm and bundle packaging. | |
| stealth/space-bunny-alpha | — | closed resolved | Implemented by merged PRs #279–#281, culminating in commit fe2d065f: packed charms and bundles now include a generated manifest.yaml with build metadata. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. The feature to auto-generate a build-time manifest.yaml with version, timestamp, OS, and architecture metadata was abandoned or superseded. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation due to inactivity. The request to auto-generate a build manifest was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation, likely abandoned. The request to auto-generate a manifest.yaml with build metadata during charm or bundle packing was not addressed. No pull requests, comments, or resolution details were recorded. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Feature request to generate a build-time manifest.yaml with version, timestamp, OS, and architecture details was abandoned. The issue was closed without implementation or discussion. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/charmcraft#281
(confidence 100%)
Completed manifest generation and merged as commit fe2d065f.
-
Likely Fixed By:
canonical/charmcraft#279
(confidence 98%)
Initial implementation of manifest generation during packing.
-
Likely Fixed By:
canonical/charmcraft#280
(confidence 98%)
Added the manifest-creation helper.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #279 Produce a manifest when building charms and bundles. | charmcraft | merged | Merged #279 in commit 92f43316 to generate build manifests for charms and bundles; follow-ups #280 and #281 completed helper and packed-output integration. | |
| #280 Added a helper to create a manifest | charmcraft | merged | Merged PR #280 in commit f13e7bbc, adding a reusable manifest-creation helper for upcoming charm and bundle builders. | |
| #281 Include a manifest in the built result when packing charms and bundles. | charmcraft | merged | Merged PR #281 as fe2d065f, adding generated manifests to packed charm and bundle results and fixing #273. |