refactor(identity-webhook): remove legacy-env, ship 0.4.0#8
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Cover handleAuthorize + createOidcVerifier end-to-end: JWT auth, composite app_<24hex>_<secret> exchange, and live balance-gate 483 / expiry capping. (legacy-env was never present on the livepeer upstream stack.)
Drop ./legacy-env; ship protocol + verifiers + balance-gate only. Point repository metadata at pymthouse/clearinghouse for npm provenance.
Next release after 0.3.3; tip already exports balance-gate without legacy-env.
2e32355 to
aeb1d7f
Compare
|



Summary
./legacy-env(and tests); consumers usecreateEndUserVerifierFromEnv+createBalanceGate../protocol,./verifiers,./balance-gate.pymthouse/clearinghouse(renamed from clearinghouse-runtime).This tip is what pymthouse should depend on after publish (
@pymthouse/clearinghouse-identity-webhook@^0.4.0), fixing the finding that published0.3.3lacked./balance-gate.Test plan
cd identity-webhook && npm testv0.4.0, confirm npm trusted publisher is set forpymthouse/clearinghouse+release.yml^0.4.0