Skip to content

chore(main): release 1.0.0#60

Closed
sid-release-bot[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--opaque-workspace
Closed

chore(main): release 1.0.0#60
sid-release-bot[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--opaque-workspace

Conversation

@sid-release-bot

@sid-release-bot sid-release-bot Bot commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.0.0 (2026-06-30)

Features

  • OPAQUE (RFC 9807) PAKE client with password-policy validation (60d9a07)

Bug Fixes

  • opaque-zkpp: deploy threaded wasm variants + wire backend-wasm to generate_zkpp_proof (b43a8c9)

Performance Improvements

  • opaque-zkpp: persistent worker pool reused across stages + commit-MSM worker (41b46a4)

This PR was generated with Release Please. See documentation.

@codecov

codecov Bot commented Jun 30, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@sid-release-bot sid-release-bot Bot force-pushed the release-please--branches--main--components--opaque-workspace branch from 64cbe38 to 16a1d4d Compare June 30, 2026 01:35
@polaz

polaz commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

Superseded by the monorepo release-please config (per-package manifest: opaque=1.0.4, opaque-zkpp=0.1.0). This was from the old single-package/root mode proposing a spurious 1.0.0.

@polaz polaz closed this Jun 30, 2026
@polaz polaz deleted the release-please--branches--main--components--opaque-workspace branch June 30, 2026 07:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant