Commit ee37fad
Publish 1.2.1, the first version a tag can point at
Two loose ends from the release, closed in one bump rather than two, because in
this repo touching pyproject.toml *is* the publish - a cosmetic commit and a
tagging commit would each have cost a Registry version.
Drops the Banner key. The Registry accepts it, stores it and never renders it;
only Icon reaches Manager. Leaving the key in advertises an artwork slot that
does not exist. The image stays in docs/assets - it costs nothing there and the
Registry may grow the slot back.
The number is what the tag and the GitHub release will now both say. Until now
the release page said v1.0.0 while the manifest said 1.2.0 and Manager served
1.1.0 - three answers to one question. 1.2.1 is one answer.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>1 parent 84b7df9 commit ee37fad
2 files changed
Lines changed: 10 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | | - | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
4 | 10 | | |
5 | 11 | | |
6 | 12 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | 3 | | |
4 | | - | |
| 4 | + | |
5 | 5 | | |
6 | 6 | | |
7 | 7 | | |
| |||
20 | 20 | | |
21 | 21 | | |
22 | 22 | | |
| 23 | + | |
23 | 24 | | |
24 | | - | |
| 25 | + | |
25 | 26 | | |
26 | 27 | | |
27 | 28 | | |
0 commit comments