Repository navigation
chore(release): v0.1.0-alpha.1 - #6
Merged
Merged
Conversation
added 10 commits
October 7, 2026 10:34
An installed tool has no Directory.Build.props next to it, so every component was recorded as the 0.1.0 fallback and 'update' could never see a newer version. The build already stamps the package version into the assembly; read it from there.
Parts such as dialog-trigger look up their parent type at runtime, and parents depend on their parts, so 17 parts did not compile when added alone. 'add <part>' now installs the part's family instead. The install summary also printed nothing, because the success and skip counters were passed by value.
…release notes The workflow restored and built the bare src/ folder, which has no project file, so no release could have succeeded. It now builds the CLI and test projects, fails when the tag doesn't match the Directory.Build.props version, runs the tests, and uses the version's section of docs/RELEASE_NOTES.md as the GitHub release body. prepare-release.ps1 packs only the CLI; Core and Templates ship inside it.
… prerelease Install with --prerelease, since only a prerelease is published. README and QUICKSTART examples now use the real API (no Variant="Primary" or CardTitle), QUICKSTART loads the theme, and the roadmap and development plan match what is merged. Avalonia target is 12.x.
pr-check.yml runs 'dotnet format --verify-no-changes' on the CLI project, which failed on main because of trailing whitespace in five files. Whitespace only.
Ports ShellUI's terminal loaders with the ShellUI Native mark (two screens): init and list open with the mark, version and a subtitle in place of the ASCII banner; init's setup draws the mark dot by dot beside the current step; add uses the snake spinner. Without an interactive Unicode terminal they fall back to the snake spinner or plain text. init no longer waits 300 ms behind a spinner to detect the project.
…kdown nuget.org renders Markdown only, so the <picture> block at the top of the CLI README showed as raw HTML. It now uses a 64 px PNG of the mark. Both READMEs list ShellUI, ShellIcons and ShellDocs with their marks; the PNGs were drawn with md-files brand/generate.py.
nuget.org accepts SVG images from raw.githubusercontent.com, which serves them as image/svg+xml. The SVGs are the brand favicon tile (ink on light, paper on dark via prefers-color-scheme) with their size set in the file, since Markdown can't size images. They replace the 64 px and 48 px PNGs.
The mark above the ASCII banner used absolute raw.githubusercontent.com URLs, which return 404 while the repository is private, so no logo showed. The header now matches ShellUI's: a <picture> with light and dark bare-dot logos (200 px, same dot size, spacing and off-dot opacity as ShellUI's) by relative path, a centred title, tagline and badges, and no ASCII banner. The NuGet badge shows prereleases. assets/icon-dark.png is no longer used.
github-actions
Bot
added
documentation
Same setup as ShellDocs: the release job runs in the 'release' environment with id-token: write, and NuGet/login exchanges the GitHub OIDC token for a one-hour API key, so no long-lived NUGET_API_KEY secret is stored; only NUGET_USER (the nuget.org profile name). Also from ShellDocs: a manual dry run that packs and validates without publishing, and a check that stops the run when the version is already on nuget.org. docs/RELEASING.md has the one-time setup.
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
1 participant
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.
Summary
Prepares the first NuGet prerelease of
ShellUI.Native.CLI(MAUI only).Release
0.1.0-alpha.1inDirectory.Build.propsrelease.yml: builds the CLI and test projects (the baresrc/folder has no project file), fails when the tag doesn't match the props version, runs the tests, and uses the version's section ofdocs/RELEASE_NOTES.mdas the GitHub release body (scripts/extract-release-notes.sh;.gitattributeskeeps*.shLF)prepare-release.ps1packs only the CLIdocs/RELEASE_NOTES.mdCLI
0.1.0add <part>installs the part's whole family (add dialog-trigger→dialog); 17 parts did not compile when added aloneinitandlistopen with the mark instead of the ASCII banner,initdraws it dot by dot while setting up,adduses the snake spinner; plain fallbacks without an interactive terminaldotnet format --verify-no-changes(pr-check) passesDocs
--prerelease; README and QUICKSTART examples use the real API (noVariant="Primary"/CardTitle); QUICKSTART loads the themeVerification
dotnet build ShellUI.Native.slnx: 0 warnings; tests 511/511; each commit builds and passes on its ownmy-appbuild with 0 warnings on android, ios, maccatalyst and windows0.1.0-alpha.1; the README example runs on Windows