chore(deps): bump actions/setup-dotnet from 5.1.0 to 5.2.0 - #2
Merged
Aaronontheweb merged 1 commit intoMay 20, 2026
Merged
Conversation
dependabot
Bot
added
dependencies
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions/setup-dotnet-5.2.0
branch
from
May 10, 2026 15:56
fae328f to
c104a61
Compare
This was referenced May 10, 2026
Aaronontheweb
added a commit
that referenced
this pull request
May 10, 2026
Implements the bash lexer per SPEC §5 plus the shared opaque-region scanner that bash uses for $(...) and backtick boundary tracking (grammar-agnostic so v0.2 PowerShell can reuse it). Locked interpretation #2 from openspec/changes/v0.1-locked-interpretations applied: - $(cmd) and `cmd` collapse into one OpaqueSubstitution token; the parser will consume these as Arg{Kind=DynamicSkip, IsPath=false} so surrounding clauses stay parseable. - $((expr)) and ${var//pat/repl} emit UnparseableSentinel tokens; the parser will set ParsedCommand.IsUnparseable=true. All new types under src/ShellSyntaxTree/Internal/{Lexing,Bash/Lexing}/ are internal. InternalsVisibleTo("ShellSyntaxTree.Tests") added so the test project can exercise them directly. 78 new unit tests (16 OpaqueRegionScanner + 62 BashLexer) covering every SPEC §5 token kind, all operators, quote handling, escape handling, opaque-region collapse, unbalanced quotes, heredoc skip, and the four unparseable-sentinel triggers. Combined with PR 1's 18 tests: 96/96 passing on net10.0. SPEC.md updated: - §1 non-goals now explicitly addresses command substitution behavior - §5 adds OPAQUE_SUBSTITUTION + UNPARSEABLE_SENTINEL token kinds, the <<- heredoc operator, simple ${VAR} absorption into Word - §11 adds arithmetic + complex-param-expansion to IsUnparseable triggers (parser will materialize this in PR 3) OpenSpec tasks.md updated to mark Phase 1 fully complete and Phase 2 implementation done; Phase 2 commit/push happens via this PR.
2 tasks
Aaronontheweb
added a commit
that referenced
this pull request
May 10, 2026
Implements the verb tables from SPEC §6 and a working BashCommandParser
that wires PR 2's lexer tokens into the public AST. BashParser.Parse no
longer throws — the v0.1 contract starts working end-to-end (in
literal-only mode; path classification + cd-attribution land in PRs 4-5).
What's wired:
- BashArity, CwdVerbs, FileVerbs, FlagsWithValue, ControlFlowKeywords
(Internal/Bash/Verbs/BashVerbs.cs)
- Compound splitting on &&, ||, ;, |
- Verb chain longest-prefix probe (joining 1, 2, 3 tokens; first hit wins)
- Args + redirects per clause; OpaqueSubstitution → Arg{Kind=DynamicSkip}
- UnparseableSentinel (arithmetic, complex param) → ParsedCommand.IsUnparseable
- Anomaly safe-fail (SPEC §11): control-flow keywords, function defs,
process substitution, unbalanced parens
- Subshell + bash -c framework (inner-clause splitting + quoted-string
literal; full attribution + recursion in PR 5)
53 parser unit tests + 50 corpus entries (10 simple-verb, 10 multi-token,
15 compound, 10 redirect, 5 unparseable). Combined with PR 1+2: 199/199
passing.
CorpusRunnerTests skeleton uses [Theory] [MemberData] over
tests/.../Corpus/bash/*.json with field-by-field comparison; polished
AstAssert.Equal helper arrives in PR 6.
SPEC.md §7 updated:
- FlagsWithValue value type is HashSet<string> (not IReadOnlySet<string>)
for netstandard2.0 compat
- Added PR 4 follow-up note: verb-chain probe must run AFTER
flag-with-value consumption for inputs like `git -C /repo log` to
produce Verb.Tokens=["git", "log"] per SPEC §12 example
Locked interpretations applied:
- #2 (command substitution): OpaqueSubstitution tokens collapse into
one DynamicSkip arg; UnparseableSentinel triggers IsUnparseable
- #4 (bash -c overflow): framework only in PR 3; PR 5 adds the depth-5
cap that uses ParsedCommand.IsUnparseable
PR 3 follow-ups tracked in openspec/changes/v0.1-locked-interpretations/tasks.md
(flag-with-value-aware probe, path classification corpus updates).
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions/setup-dotnet-5.2.0
branch
3 times, most recently
from
May 11, 2026 14:16
93f13d8 to
4664617
Compare
Aaronontheweb
enabled auto-merge (squash)
May 11, 2026 15:28
Bumps [actions/setup-dotnet](https://github.com/actions/setup-dotnet) from 5.1.0 to 5.2.0. - [Release notes](https://github.com/actions/setup-dotnet/releases) - [Commits](actions/setup-dotnet@v5.1.0...v5.2.0) --- updated-dependencies: - dependency-name: actions/setup-dotnet dependency-version: 5.2.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions/setup-dotnet-5.2.0
branch
from
May 20, 2026 03:28
4664617 to
24e637b
Compare
Aaronontheweb
deleted the
dependabot/github_actions/actions/setup-dotnet-5.2.0
branch
May 20, 2026 03:30
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.
Bumps actions/setup-dotnet from 5.1.0 to 5.2.0.
Release notes
Sourced from actions/setup-dotnet's releases.
Commits
c2fa09fBump minimatch from 3.1.2 to 3.1.5 (#705)02574b1Add support for optional architecture input for cross-architecture .NET insta...16c7b3cBump fast-xml-parser from 4.4.1 to 5.3.6 (#671)131b410Add support for workloads input (#693)