chore(release): walk src/*/*.csproj in publish; drop release-as override#26
Merged
Merged
Conversation
…-as override Two small followups to the 2.0.2 publish: 1. release-please.yml's publish job was hardcoded to pack only src/ZeroAlloc.Authorization/ZeroAlloc.Authorization.csproj. When the standalone ZeroAlloc.Authorization.Generator project landed in 2.0.1, release-please continued packing only the main package — the rescue publish-from-manifest.yml workflow was needed to push the Generator package. This patch loops over src/*/*.csproj like publish-from-manifest.yml does, so future sub-package additions publish automatically. dotnet pack on IsPackable=false projects produces no .nupkg, so the loop is safe. The test step also dropped its hardcoded path (tests/ZeroAlloc.Authorization.Tests/...) and now runs the full solution's tests via plain `dotnet test`. This catches regressions in any new test project (PackSmoke, future suites) without further workflow edits. 2. release-please-config.json drops "release-as": "2.0.2". 2.0.2 has shipped; conventional-commit-driven bumps are correct from here on. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
Two small followups to the 2.0.2 publish:
release-please.ymlpublish job walkssrc/*/*.csprojinstead of hardcodingsrc/ZeroAlloc.Authorization/...csproj. When the standaloneZeroAlloc.Authorization.Generatorproject landed in 2.0.1, this workflow continued packing only the main package — the rescue `Publish from manifest` had to step in for both 2.0.1 and 2.0.2 publishes to push the Generator package. With this change, future sub-package additions publish automatically. `dotnet pack` on `IsPackable=false` projects produces no .nupkg, so the loop is safe.The test step also drops its hardcoded
tests/ZeroAlloc.Authorization.Tests/...path and now runs the full solution via `dotnet test`. This picks up new test projects (e.g. `PackSmoke`) without further workflow edits.release-please-config.jsondrops\"release-as\": \"2.0.2\"— 2.0.2 has shipped; conventional-commit-driven bumps are correct from here.Why bundled
Both are tiny diffs touching the publish/release plumbing only; bundling avoids two trivial admin-bypass merges. No source/runtime changes.
Test plan
Publish from manifestrescue should not be needed)🤖 Generated with Claude Code