chore: v0.0.2, and the release notes admit the AppImage exists - #84
Merged
Conversation
Sixty-four commits since v0.0.1. Three are worth a reader's attention because each was something the application claimed and did not do: The commit graph rendered at a fifth of the window while `UI_SPEC`'s first principle promised it "the most pixels" — a `FillPortion` sat inside a container with no height, so the detail pane took everything left over. Every confirmation, action sheet and prompt dimmed the screen with black rather than with the theme, so on the light theme those were the only things on screen darkened that way. Button labels were white on the accent, which measures 3.21:1 on the dark theme and fails WCAG AA. The contrast suite covered text as a colour and never a label on one. Also in: submodules, worktrees and Git LFS end to end, `--autosquash` with a draggable rebase plan, a Brazilian Portuguese translation, and the three token scales the interface is now built from. The release notes gain the AppImage. It has been built, verified and uploaded by the workflow since #53 — the job even runs it to check it starts — but the download table listed three platforms and the Linux row named only the tarball, so the one file that needs no unpacking was the one nobody was told about.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version bump for v0.0.2, plus one thing found while checking the release path.
What is in it
Sixty-four commits since v0.0.1. Three are worth a reader's attention, because each was something the application claimed and did not do:
UI_SPEC's first principle promised it "the most pixels". AFillPortionsat inside a container with no height, so the detail pane took everything left over. (#77)Also in: submodules, worktrees and Git LFS end to end;
--autosquashwith a draggable rebase plan; a Brazilian Portuguese translation; and the three token scales the interface is now built from.The thing found while checking
The release notes never mentioned the AppImage. It has been built, verified and uploaded by the workflow since #53 — the job even runs it to check that it starts — but the download table listed three platforms and the Linux row named only the tarball. The one Linux file that needs no unpacking was the one nobody was told about, while the README has been advertising it.
Fixed in the same change: the table lists it, and the Linux instructions lead with
chmod +xand running it.Checked before tagging
Cargo.tomlhas four0.0.1references, not one — the workspace version and three path dependencies. All four bumped,Cargo.lockregenerated.CFBundleShortVersionStringfrom the manifest./releases/lateststill 404s and the README still points at/releases. Unchanged and intended.Next
Tag
v0.0.2once this is onmain; the workflow builds on three runners and attaches the archives plusSHA256SUMS.txt.