Skip to content

chore(release): prepare v0.9.2 - #81

Merged
MichalCz merged 1 commit into
mainfrom
release/v0.9.2
Sep 29, 2026
Merged

MichalCz merged 1 commit into
mainfrom
release/v0.9.2

Conversation

@MichalCz

Copy link
Copy Markdown
Member

Intended result

Prepare the stable v0.9.2 patch release on protected main after Broker-session PR #80 merged. This PR does not publish packages or create a tag.

Changes

  • Set all six workspace package versions and internal dependency pins to 0.9.2, including package-lock.json.
  • Set Python pyproject.toml and uv.lock metadata to the canonical stable 0.9.2 version.
  • Add v0.9.2 changelog notes for concurrent authenticated Broker sessions and cancelled WebSocket opens.

Validation

  • npm test: partition 1 387/387 passed; partition 2 173 passed, 4 skipped; no failures.
  • npm run lint and git diff --check: passed.
  • Stable tag policy for 0.9.2: npmjs.org latest, Python 0.9.2; post-release development version 0.9.3-next.0.

After this PR is merged through the protected workflow, tag that merged main commit as v0.9.2 in a separate confirmed action. The tag starts the maintainer-gated npmjs.org release and GitHub Python asset workflow.

Align JavaScript and Python package metadata and internal pins for the stable patch release, and document concurrent Broker sessions and cancellation in the changelog.
@MichalCz
MichalCz merged commit 520cede into main Sep 29, 2026
13 checks passed
@MichalCz
MichalCz deleted the release/v0.9.2 branch September 29, 2026 10:24
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