Skip to content

release: AHP 1.0.0 - #495

Closed
Connor Peet (connor4312) wants to merge 2 commits into
mainfrom
release/ahp-1.0.0
Closed

Connor Peet (connor4312) wants to merge 2 commits into
mainfrom
release/ahp-1.0.0

Conversation

@connor4312

Copy link
Copy Markdown
Member

Summary

  • Prepare AHP 1.0.0 for the spec and all six clients: Rust, Kotlin, TypeScript, Swift, Go, and .NET.
  • Consume all 26 changelog fragments into seven release entries dated 2026-10-02, folding the unreleased 0.10.0 spec entry into 1.0.0.
  • Update all native client versions, Rust workspace dependency pins, lockfiles, generated version constants, and release metadata.
  • Remove the pre-existing handwritten .NET Unreleased notes as requested; retain the fragment-derived 1.0.0 entry and all previous release entries.
  • In a separate second commit, advance the development protocol version to 1.1.0, retaining 1.0.0 and existing negotiation fallbacks.

Merge strategy

Merge this PR with a merge commit, not squash. Release tags must point to the first commit, where the protocol and all native package versions are 1.0.0. The second commit speaks development protocol 1.1.0 and must not be tagged for this release.

Validation

  • npm run generate and npm test passed for both release and post-release states: 515 tests, with 100% reducer branch coverage.
  • TypeScript client npm run build and npm test passed: 77 tests.
  • npm run verify:changelog passed after the .NET notes cleanup.
  • Verified all seven release entries and client metadata at the release SHA, every consumed fragment message in each targeted release entry, and separation of release/development protocol versions.
  • Per-language builds and conformance tests are covered by PR CI.

After merge: publish 1.0.0

All seven tags must use this exact release commit:

(
set -e
RELEASE_SHA=8161249f55f65b4fb60948e59be37f261bf4b151
git fetch origin main
git merge-base --is-ancestor "$RELEASE_SHA" origin/main

git tag spec/v1.0.0 "$RELEASE_SHA"
git tag rust/v1.0.0 "$RELEASE_SHA"
git tag kotlin/v1.0.0 "$RELEASE_SHA"
git tag typescript/v1.0.0 "$RELEASE_SHA"
git tag v1.0.0 "$RELEASE_SHA"
git tag clients/go/v1.0.0 "$RELEASE_SHA"
git tag dotnet/v1.0.0 "$RELEASE_SHA"

git push origin spec/v1.0.0
git push origin rust/v1.0.0
git push origin kotlin/v1.0.0
git push origin typescript/v1.0.0
git push origin v1.0.0
git push origin clients/go/v1.0.0
git push origin dotnet/v1.0.0
)

Stop if the ancestry check fails. Push tags individually so each publication trigger receives its own push event.

Spec, Rust, Swift, and Go publication runs appear in GitHub Actions. Kotlin, TypeScript, and .NET publish through Azure DevOps, not GitHub Actions; verify their runs in the AHP pipelines in vscode-engineering. .NET publication requires approval.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@connor4312

Copy link
Copy Markdown
Member Author

Superseded by #499, which includes the requested supported-version baselines and host-side SemVer negotiation in a rebuilt two-commit 1.0.0 release. Branch protection prevented replacing this PR's history. The new release SHA is 5f16d81.

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