Trusted Publishing on nuget.org; publish 2.0 as 2.0.0-preview.1

[Astn]

Two things the owner asked for on 2026-09-25.

Trusted Publishing. The policy on nuget.org (owner AustinHarris, publisher GitHub Actions, repository Astn/JSON-RPC.NET, workflow build_publish_master.yml) replaces the stored API key.

• The master workflow gets id-token: write and contents: read; NuGet/login@v1 exchanges the OIDC token for a one-hour API key right after the tests, with user: AustinHarris; the push uses that key and keeps --skip-duplicate.
• The NugetKey secret is no longer referenced anywhere and can be deleted from the repository settings.
• The pull-request workflow's non-fatal push of ci- suffixed packages is removed, along with the --version-suffix it needed: the policy is bound to the master workflow file, so that push could only fail from now on.

Preview. VersionSuffix is preview.1 on the four packages, so the master build packs 2.0.0-preview.1 (a --version-suffix on the command line still overrides it). The README's Installation says --prerelease and why, Versioning and support gains a Previews bullet, and the changelog heading names the preview.

Merging this triggers the master workflow, which publishes the four 2.0.0-preview.1 packages through the new policy. The earlier failed run cannot be re-run for this: a re-run uses the workflow file as it was.

Project URL. PackageProjectUrl on the four packages now points at the documentation site (https://astn.github.io/JSON-RPC.NET/, and the package's own page for the three companions); RepositoryUrl stays on GitHub.

Windows Phone 7. The AustinHarris.JsonRpc.Client.WP7 and AustinHarris.JsonRpc.Client.WP7Test projects are removed; the platform is no longer supported and nothing in 2.0 built from them.

Packaging. Every package now ships its XML documentation, a Source Link symbols package (.snupkg, built with ContinuousIntegrationBuild on master and pushed alongside the .nupkg), the site favicon as its icon, tags naming the target frameworks (nuget.org also lists them from the lib/ folders), and release notes that say what 2.0 is and link to the What is new and Upgrading from 1.x pages on the documentation site. Verified locally by packing all four and inspecting the .nuspec and contents.

Package README. The core shipped the repository README, which nuget.org renders without its HTML, relative links or images. Json-Rpc/README.md is written for that page (absolute links, the headline chart from raw.githubusercontent.com, a short Upgrading from 1.x summary) and points a 1.x user at What is new and Upgrading right after the install line; Visual Studio opens the package README on install and update, which is the only install-time hook NuGet still offers (install scripts were removed with PackageReference). The companion READMEs open the same way and the four descriptions are shorter. The chart URL resolves once #154 is on master.

Site. CHANGELOG.md is published as changelog.html (What is new) and the README's Upgrading from 1.x section moves to docs/upgrading.md, published as upgrading.html, so the package links land on their own pages; the README keeps a summary and links.