Skip to content

WPB-23631: Move Brig.Effects.JwtTools in Wire.JwtTools - #5396

Open
blackheaven wants to merge 1 commit into
developfrom
gdifolco/WPB-23631-migrate-brig-galley-spar-effects-10
Open

WPB-23631: Move Brig.Effects.JwtTools in Wire.JwtTools#5396
blackheaven wants to merge 1 commit into
developfrom
gdifolco/WPB-23631-migrate-brig-galley-spar-effects-10

Conversation

@blackheaven

Copy link
Copy Markdown
Contributor

https://wearezeta.atlassian.net/browse/WPB-23631

Checklist

  • Add a new entry in an appropriate subdirectory of changelog.d
  • Read and follow the PR guidelines

Move the JwtTools effect + interpreter to Wire.JwtTools. Carry-along type move
in the same commit (diff-ordered before the port): CertEnrollmentError moves
from Brig.API.Types into Wire.JwtTools (not wire-api -- its RustError constructor
wraps the jwt-tools FFI DPoPTokenGenerationError type, which must not leak into
the pure types package). Constructors preserved verbatim; Brig.API.Error and
Brig.User.Client now import it from Wire.JwtTools. Adds the jwt-tools build-dep.
Rewire consumers (CanonicalInterpreter, Brig.API.Public); delete old module;
register in cabal.
@blackheaven
blackheaven requested review from a team as code owners July 29, 2026 18:15
@blackheaven blackheaven added the ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist label Jul 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant