fix: order the yaml output
Metadata
Current evaluation
Merged #68 via commit f5d94a77, ordering YAML output as identity/description fields, base/platform data, metadata links, and finally parts.
Resolution: closed resolved
Reason: PR #68 was merged into main as commit f5d94a77. Its changes enforce the expected YAML key order and update the corresponding output tests.
Evaluated by: mr-cal-bot
No scores available.
Issue body
This follows the expectations for Craft Applications of having name, version, summary and description. Followed by the base/platform data, then closing with the metadatalinks. And finally, parts.
- [ ] Have you followed the guidelines for contributing?
- [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [ ] Have you successfully run `tox`?
-----
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged #68 via commit f5d94a77, ordering YAML output as identity/description fields, base/platform data, metadata links, and finally parts. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged #68 (commit f5d94a77) to fix YAML output ordering: name, version, summary and description, then base/platform, metadatalinks and parts. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged PR reordering YAML output to match Craft Applications standards. Fields now follow name, version, summary, description, base/platform, metadatalinks, and parts order. Approved by two reviewers, passed CI, and integrated into main. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #65 fix: correctly represent yaml dumped multiline strings | craft-application | merged | Merged PR #65 added a YAML representer so multiline strings dump correctly; PR commit 85bb6a0 landed in main as 51346d9b. |