Adopt GitHub Release-based publishing with tag-driven versioning and changelog

[Copilot]

This revisits release creation to align package publishing with GitHub’s standard release flow. Releases now originate from GitHub Releases, with versioning derived from the release tag and changelog/release notes managed in one place.

• Release workflow

  • Replaced the manual workflow_dispatch NuGet publish workflow with a release.published workflow.
  • Validates vX.Y.Z / vX.Y.Z-suffix tags and uses the tag version for build + pack.
  • Publishes the packed artifact to NuGet from the release event.

• Versioning + package metadata

  • Moved the project from a hardcoded <Version> to <VersionPrefix> so release builds can inject the actual package version.
  • Simplified package release notes metadata to point to CHANGELOG.md and the GitHub Releases page.
  • Included CHANGELOG.md in the NuGet package alongside the existing README.

• Changelog + GitHub release notes

  • Added CHANGELOG.md as the maintained history for shipped versions and upcoming changes.
  • Migrated the full historical release notes into the new structured changelog format, back to 1.2.0.
  • Added .github/release.yml so GitHub-generated release notes are grouped by release-relevant categories.

• Repository docs

  • Documented the release flow in README.md:
    1. update CHANGELOG.md
    2. create a GitHub Release with a version tag
    3. let the release workflow publish the matching NuGet version

Example of the new release contract:

on:
  release:
    types: [published]

# tag: v3.0.1
# package version: 3.0.1

[ThomasPe]

@copilot migrate full changelog to new format.

[Copilot]

@copilot migrate full changelog to new format.

Done in bc16f39. CHANGELOG.md now includes the full historical release history in the new structured format, migrated from the old package release notes metadata.

[Copilot]

Pull request overview

Aligns WordPressPCL’s NuGet publishing with GitHub’s release flow by making GitHub Releases (and their tags) the source of truth for versioning and publishing.

Changes:

• Switch NuGet publishing workflow to trigger on release.published, validate vX.Y.Z[-suffix] tags, and inject the tag-derived version into build/pack.
• Move package versioning to <VersionPrefix> and streamline release notes metadata to reference CHANGELOG.md + GitHub Releases.
• Add and document CHANGELOG.md and GitHub release-notes configuration (.github/release.yml).

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
WordPressPCL/WordPressPCL.csproj	Uses VersionPrefix, simplifies release notes metadata, and includes CHANGELOG.md in the NuGet package.
README.md	Documents the new GitHub Release-based publishing process.
CHANGELOG.md	Introduces a centralized changelog for release history and upcoming changes.
.github/workflows/publish-nuget.yml	Publishes to NuGet on GitHub Release publish, deriving package version from tag.
.github/release.yml	Configures GitHub-generated release notes categorization by labels.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.