Skip to content

Add README status badges and broaden the phase-milestone rule - #23

Merged
lgamorim merged 3 commits into
masterfrom
feature/M16-readme-badges
Aug 14, 2026
Merged

Add README status badges and broaden the phase-milestone rule#23
lgamorim merged 3 commits into
masterfrom
feature/M16-readme-badges

Conversation

@lgamorim

@lgamorim lgamorim commented Aug 14, 2026

Copy link
Copy Markdown
Owner

Summary

  • Add a status badge row (CI, Docs, NuGet, License — in that order) under the README.md title. The NuGet badge already resolves to v1.0.0-rc.1 (orange, shields' prerelease color) since the candidate is on nuget.org, and flips to a blue v1.0.0 automatically at the stable publish. Downloads and per-package badges are deliberately omitted.
  • Amend the phase-milestone rule in .claude/rules/project/sqlbound.md: phase milestones now collect every PR merged while the phase is in flight, not just M-number PRs, so the milestone reads as the complete record of what the phase ships. Run the CI build/test matrix on Linux, Windows, and macOS #17Adopt the claude-rules library-team profile as the shared ruleset #22 were associated with the Phase 6 milestone retroactively under this reading.
  • Align the release-candidate rule with practice: candidates are published to nuget.org as prereleases so real consumers can validate them before GA, replacing the outdated claim that rc tags record the candidate as unpublished.

All changes are documentation/process-only; no code or packaging is touched.

🤖 Generated with Claude Code

lgamorim and others added 2 commits August 14, 2026 21:19
Give README readers the at-a-glance signals a library consumer looks
for: CI health on master, the documentation site, the published NuGet
version of the core package, and the license. The two dynamic
nuget.org/GitHub badges resolve once the stable package is published;
Downloads and per-package badges are deliberately omitted to keep the
row to signals with day-one value.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The rule previously bound only M-number PRs to the phase milestone,
which left infra and maintenance PRs unassociated and made the
milestone under-report what a phase actually ships. Phase milestones
now act as the complete release bucket for the phase, answering
"what changed in this phase?" in one view.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@lgamorim lgamorim added this to the Phase 6 — Ship (1.0.x) milestone Aug 14, 2026
The rule said the annotated tag records that a candidate is not
published, but 1.0.0-rc.1 is live on nuget.org: candidates go out as
prerelease packages so real consumers can validate them before GA.
Align the rule with the practice.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@lgamorim
lgamorim merged commit cfc18a4 into master Aug 14, 2026
8 checks passed
@lgamorim
lgamorim deleted the feature/M16-readme-badges branch August 14, 2026 21:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant