Skip to content

chore(release): promote 2.0.1 preparation to main - #712

Merged
SunSi12138 merged 5 commits into
mainfrom
dev
Sep 19, 2026
Merged

SunSi12138 merged 5 commits into
mainfrom
dev

Conversation

@SunSi12138

Copy link
Copy Markdown
Owner

Promote the reviewed SharpLink 2.0.1 release preparation from dev to main.

Includes:

  • VersionPrefix 2.0.1
  • 2.0.1 changelog entry
  • refreshed generated manifest fixture for the 2.0.1 generator provenance/fingerprint

The release-prep PR #711 passed the required fast check on dev.

This PR does not publish NuGet by itself. After the main release gate passes and this PR is merged, v2.0.1 will be tagged to trigger the tag-gated NuGet publication.

* chore(release): bump version to 2.0.1

* docs(release): add 2.0.1 changelog

* test(generator): refresh 2.0.1 manifest fixture
* fix(release): verify current package version

* chore(release): calibrate 2.0.1 version axes
* fix(release): use current package version in release gates

* fix(release): use current package version in release gates

* test(release): parameterize current ABI package version

* test(release): parameterize current ABI package version
Revert the squash merge of PR #706.

The merge happened without the maintainer's approval: the review prompt
template still instructed the reviewer to merge once CI was green, so the
review conversation merged the PR and closed issue #691 automatically.
Merging is a human decision and must not be delegated to the review step.

This restores dev to the state before the merge; the work itself remains
available on the issue-691-generation-control branch and can be merged
again once explicitly approved.

Refs #691
@SunSi12138
SunSi12138 merged commit f41bb79 into main Sep 19, 2026
93 checks passed
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