Repository navigation
docs: declare the public API stable and prepare for 1.0.0 - #20
Merged
Merged
Conversation
Replaces README's "APIs and behavior may change before the first stable release" with an explicit stability statement, now that the full release validation (docs/Compatibility.md) is complete and the minimum-version commitment has been confirmed. Updates every stale beta.4/beta.5 version reference (README's version matrix and install command, Usage-Guide's install command, Release-Process's "next planned release" and example tag commands) to target 1.0.0, and removes Directory.Build.props's VersionSuffix so a local dotnet pack no longer produces a beta-labeled artifact. The release workflow itself already derives the published version from the git tag, so this only affects local/dev builds and documentation, not what previously shipped. Also corrects README's "build-verified through 31.7.2" to 31.8.4 to match the current Compatibility.md record. Tagging and publishing v1.0.0 itself are separate, deliberate follow-up actions, not part of this change.
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
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
docs/Compatibility.mdis complete and the minimum-version commitment has been confirmed.beta.4/beta.5version reference to1.0.0: README's version matrix and install command,Usage-Guide.md's install command, andRelease-Process.md's "next planned release" line and example tag commands.Directory.Build.props'sVersionSuffixso a localdotnet packproduces1.0.0instead of a beta-labeled artifact. Confirmed this builds and packs cleanly. The release workflow (release.yml) already derives the published version from the git tag via-p:PackageVersion, so this only affects local/dev builds and documentation — not what has already shipped.31.8.4to match the currentCompatibility.mdrecord.Not included, intentionally: tagging and publishing
v1.0.0itself. Those are separate, higher-stakes actions (an immutable NuGet publish) left for a deliberate follow-up once you're ready to pull that trigger.Test plan
dotnet buildclean (0 errors).dotnet test— 90/90 pass.dotnet packlocally confirmed to produceXperienceCommunity.FormsToolkit.1.0.0.nupkg(no beta suffix).