fix: format snapcraft-started-at timestamps
Metadata
Current evaluation
Merged in canonical/snapcraft#5416 (f16a1aedf), fixing core20 manifest timestamps and adding regression coverage; the fix shipped in Snapcraft 8.8.1.
Resolution: closed resolved
Reason: PR #5416 was merged as commit f16a1aedf and explicitly fixed #5413. It formats snapcraft-started-at as an ISO timestamp and adds regression tests for core20, core22, and core24.
Evaluated by: mr-cal-bot
No scores available.
Issue body
- [x] Have you followed the [guidelines for contributing](https://github.com/canonical/snapcraft/blob/main/CONTRIBUTING.md)?
- [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [x] Have you successfully run `make lint`?
- [x] Have you successfully run `make test`?
---
Fixes a regression where core20 snaps would have an invalid timestamp for `snapcraft-started-at` in their `snap/manifest.yaml`.
This regression occurred when we replaced a [deprecated `datetime.utcnow()` call](https://github.com/canonical/snapcraft/commit/f24c83d6b6e218cf18fe8c0380f964ae2ed09115#diff-fc9be1807504ea06b6c1703a5d6112665cccf6a14148fdfab685188ecfeda857L69).
core22 and core24 are unaffected, but I added regression tests to ensure they don't break in the future.
Fixes #5413
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged in canonical/snapcraft#5416 (f16a1aedf), fixing core20 manifest timestamps and adding regression coverage; the fix shipped in Snapcraft 8.8.1. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #5416 as f16a1aedf, fixing invalid core20 snapcraft-started-at manifest timestamps; released in Snapcraft 8.8.1. Added core22/core24 regression tests. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged fix for a regression causing invalid snapcraft-started-at timestamps in core20 manifests. Caused by replacing deprecated datetime.utcnow(). Added regression tests for core22 and core24. Resolves #5413. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged fix for a regression causing invalid snapcraft-started-at timestamps in core20 snap manifests. The issue stemmed from replacing deprecated datetime.utcnow() calls. Added regression tests for core22 and core24. Resolves #5413. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/snapcraft#5413
(confidence 100%)
The invalid snapcraft-started-at regression for core20 snaps was resolved by this merged PR.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #5413 Invalid date in manifest.yaml for core20 snaps | snapcraft | closed | Fixed malformed core20 manifest timestamps in PR #5416 (f16a1aedf), released in Snapcraft 8.8.1. | |
| #2559 manifest: expose snapcraft-started-at | snapcraft | merged | Merged PR #2559 via commit 1c283cc30, exposing snapcraft-started-at in manifest.yaml for ordering Snap Store processing. |