api/publish: allow setting custom Codename on the Release file - #1624
api/publish: allow setting custom Codename on the Release file#1624chipflake wants to merge 1 commit into
Conversation
a8b2fb9 to
3d7f17e
Compare
I would like to provide additional context on why this patch is helpful. Since #1269, aptly now allows users to publish to suites (distributions) whose literal values include slashes ( This patch allows us to emit |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1624 +/- ##
==========================================
- Coverage 77.37% 77.07% -0.31%
==========================================
Files 165 165
Lines 15747 15748 +1
==========================================
- Hits 12185 12138 -47
- Misses 2356 2408 +52
+ Partials 1206 1202 -4 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Description of the Change
Currently, when publishing via the API, the Codename is always set to the same string as the Distribution. This does not match the
aptlyCLI behaviour, where it is possible to set a-codenameflag.The CLI does not support updating the Codename after the published repo has been created (on Update), so I did not add
Codenameto the Update params here either. I think that it is ok not to support Codename updates (the Distribution cannot be changed either), but let me know if you think otherwise.We are already using this patch internally, it would be nice to have it merged so that we can use upstream builds.
Checklist
AUTHORS