PR 7: v0.1.0-alpha release prep#10
Merged
Merged
Conversation
Updates RELEASE_NOTES.md with the v0.1.0-alpha entry summarizing the shipping shape: public API surface, lexer/parser/resolver/per-verb rules, cd-attribution + subshell isolation + bash -c recursion, 115-entry corpus, PII audit, known v0.1.x limitations. The icon at assets/icon.png is already ShellSyntaxTree-specific (syntax-tree visualization on dark green background with >_ shell prompt motif; 512x512 PNG) — generated during template bootstrap and wired into Directory.Build.props from day one. Verification: - dotnet pack -c Release produces ShellSyntaxTree.0.1.0-alpha.nupkg and .snupkg cleanly - nupkg contents confirmed: icon.png, README.md, SourceLink metadata, lib/net8.0/ShellSyntaxTree.dll, lib/netstandard2.0/ShellSyntaxTree.dll - 353/353 tests passing on Linux; CI to verify Windows - nuspec metadata: id=ShellSyntaxTree, license=Apache-2.0, tags "bash shell parser ast security agent syntax-tree", projectUrl, etc. Per the autonomous PR loop plan: this PR auto-merges with squash when CI passes. **STOP after merge — do NOT push the v0.1.0-alpha tag without explicit user go-ahead.** The tag → nuget.org publish via publish_nuget.yml is irreversible. After merge, status entry left in IMPLEMENTATION_PLAN.md asking the user to push the tag manually (or to ack the agent doing it).
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
PR 7 of the v0.1.0-alpha shipping plan. Final PR before tag. Updates
RELEASE_NOTES.mdwith the v0.1.0-alpha entry; verifiesdotnet packproduces a clean.nupkgwith embedded README, icon, and SourceLink metadata.What landed
RELEASE_NOTES.md— v0.1.0-alpha entry summarizing the shipping shape: public API surface, lexer/parser/resolver/per-verb rules, cd-attribution + subshell isolation + bash -c recursion, 115-entry corpus, PII audit, known v0.1.x limitations.IMPLEMENTATION_PLAN.md— PR 7 status updated; awaiting tag-push approval.Icon
Already ShellSyntaxTree-specific — syntax-tree visualization on dark green background with
>_shell prompt motif (512x512 PNG, ~98 KB). Generated during template bootstrap and wired intoDirectory.Build.propsfrom day one.Verification (local)
dotnet build -c Release— cleandotnet test -c Release— 353/353 passingdotnet pack -c Release -o ./bin/nugetproduces:ShellSyntaxTree.0.1.0-alpha.nupkg(148 KB) withicon.png,README.md, SourceLink metadata,lib/net8.0/ShellSyntaxTree.dll,lib/netstandard2.0/ShellSyntaxTree.dllShellSyntaxTree.0.1.0-alpha.snupkg(31 KB)pwsh ./scripts/Add-FileHeaders.ps1 -Verifyopenspec validate v0.1-locked-interpretations --strictTest plan
Test-ubuntu-latestTest-windows-latestPer the autonomous PR loop plan: this PR auto-merges with squash when CI passes. The agent will NOT push the
v0.1.0-alphatag — the tag → nuget.org publish viapublish_nuget.ymlis irreversible.After merge, the agent leaves a status entry in
IMPLEMENTATION_PLAN.mdand stops the pipeline. The user (you, Aaron) decides when to push the tag:```bash
git checkout dev && git pull origin dev
git tag v0.1.0-alpha
git push origin v0.1.0-alpha
```
Once the tag pushes,
publish_nuget.ymlproduces the GitHub release + nuget.org package automatically.Post-tag follow-ups (PR 8+)
openspec/changes/v0.1-locked-interpretations/toarchive/2026-05-10-v0.1-locked-interpretations/dotnet add package ShellSyntaxTree --version 0.1.0-alphain the netclaw repo; one Netclaw integration test exercising a corpus entry through the live matcher