Skip to content

chore: move the package-validation baseline to 1.0.1 #35

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
StuartMeeks merged 1 commit into from
Aug 22, 2026
Merged

chore: move the package-validation baseline to 1.0.1 #35

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

### Changed

- **`PackageValidationBaselineVersion` moved to `1.0.1`**, now that 1.0.1 is published and restorable. From here an accidental break in the public surface fails the build against the first stable release rather than against `0.3.1`, so a break is a 2.0.0 rather than a judgement call. There is no 1.0.0 to baseline against — it was never published.

---

## [1.0.1] — 2026-08-22
Expand Down
8 changes: 6 additions & 2 deletions src/NextIteration.SpectreConsole.SelfUpdate/NextIteration.SpectreConsole.SelfUpdate.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,10 +24,14 @@
<PackageIcon>icon.png</PackageIcon>
<!--
Validate the public surface against the last shipped release, not just
framework compatibility: an accidental API break relative to 0.3.1
framework compatibility: an accidental API break relative to 1.0.1
fails the build instead of shipping.

1.0.1 is the first stable release, so from here a break against this
baseline is a 2.0.0, not a judgement call. There is no 1.0.0 to
baseline against — it was never published (see CHANGELOG).
-->
<PackageValidationBaselineVersion>0.3.1</PackageValidationBaselineVersion>
<PackageValidationBaselineVersion>1.0.1</PackageValidationBaselineVersion>
</PropertyGroup>

<ItemGroup>
Expand Down