← Back to issue list

Add `sha256` prefix to the `org.opencontainers.image.base.digest` annotations field in the image manifest.

View original Github issue

Metadata

Project
rockcraft
Number
#908
Type
issue
State
open
Author
moaazassali
Labels
Created
Updated
Closed

Current evaluation

Request to add sha256: prefix to org.opencontainers.image.base.digest annotation and base-digest in metadata.yaml for consistency with other digest fields. Code at project.py:441 still uses base_digest.hex() without prefix. No labels, no maintainer response in 431 days.

Suggested action: needs triage

Reason: The issue is well-scoped and the code at rockcraft/models/project.py:441 still uses base_digest.hex() without the sha256: prefix, confirming it remains unfixed. However, there are no labels, no maintainer comments, and no assignee after 431 days, indicating it has never been triaged. The fix is straightforward (prefix the hex with 'sha256:') but may warrant a backward-compatibility discussion since consumers may parse the annotation expecting bare hex.

Impact: 25 Quick Win: 18.75 Staleness: 72 Complexity: 25 Confidence: 78 Support Request: 5

Issue body

### What needs to get done Add `sha256` prefix to the `org.opencontainers.image.base.digest` annotations field in the image manifest. Here is an example of an image manifest generated by rockcraft: ``` { "schemaVersion": 2, "config": { "mediaType": "application/vnd.oci.image.config.v1+json", "digest": "sha256:ca3d163bab055381827226140568f3bef7eaac187cebd76878e0b63e9e442356", "size": 3 }, "layers": [ { "mediaType": "application/vnd.oci.image.layer.v1.tar+gzip", "digest": "sha256:24e08b276317a479704dc53c0e47753b3422695950853fc22446ec76faf6e8d0", "size": 9320708 }, { "mediaType": "application/vnd.oci.image.layer.v1.tar+gzip", "digest": "sha256:b4406d6046b42bf82b11d80e8c19acd2818ef44524bf64e3e7b4f330114af508", "size": 430 } ], "annotations": { "org.opencontainers.image.base.digest": "19d5218d4475ed6af714d9ea9aeff3ce57fcf90e93b062a587f5d183eddeddd9", "org.opencontainers.image.created": "...", "org.opencontainers.image.description": "...", "org.opencontainers.image.ref.name": "...", "org.opencontainers.image.title": "...", "org.opencontainers.image.version": "..." } } ``` ### Why it needs to get done It is inconsistent with the other digest fields in the image manifest like `config.digest` and `layers[i].digest`. It also makes the digest somewhat ambiguous due to the lack of the hashing algorithm when using it to look up the referenced image base.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 25
Quick Win: 18.75
Staleness: 72
Complexity: 25
Confidence: 78
Support Request: 5
needs triage Request to add sha256: prefix to org.opencontainers.image.base.digest annotation and base-digest in metadata.yaml for consistency with other digest fields. Code at project.py:441 still uses base_digest.hex() without prefix. No labels, no maintainer response in 431 days.
qwen/qwen3.6-35b-a3b
Staleness: 85
Complexity: 15
Confidence: 80
Support Request: 10
needs triage Request to add sha256 prefix to org.opencontainers.image.base.digest annotation for manifest consistency. Currently unlabelled with no maintainer response in over a year.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 15
Confidence: 85
Support Request: 10
needs triage External contributor requests adding the sha256 prefix to the org.opencontainers.image.base.digest annotation for OCI spec consistency. Unlabelled and inactive for over a year with no maintainer response.
qwen3.6-35b-a3b-mtp-q6
Staleness: 75
Complexity: 20
Confidence: 75
Support Request: 10
needs triage Request to add sha256 prefix to OCI base digest annotation for spec consistency. Unlabelled with no maintainer response in over a year. Requires triage to evaluate current relevance and implementation scope.
qwen3.6-35b-a3b-mtp-q6
Staleness: 75
Complexity: 10
Confidence: 70
Support Request: 5
needs triage Add sha256 prefix to org.opencontainers.image.base.digest annotation and base-digest metadata field for consistency. Issue remains unassigned and inactive for over 340 days, awaiting triage or implementation.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.