Skip to content

Releases: bi0nd0/relykit

RelyKit 0.1.2

Choose a tag to compare

@bi0nd0 bi0nd0 released this 21 Jul 00:19

Adds exact-issuer OpenID Connect third-party login initiation for application-bound recovery flows. The Nuxt adapter accepts GET and form POST on the configured login path, rejects caller-selected destinations, and starts a fresh state, nonce, and S256-PKCE transaction.

RelyKit 0.1.1

Choose a tag to compare

@bi0nd0 bi0nd0 released this 20 Jul 12:23
d0938e4

RelyKit 0.1.1 makes provider logout reliable for both current and pre-upgrade application sessions.

  • Sessions with retained ID-token evidence continue to keep the token out of browser URLs by using a protected form POST.
  • Pre-upgrade sessions without that evidence use a state-bound top-level request, allowing the identity provider to show its sign-out confirmation and end the active session.
  • The core package, Nuxt adapter, provider fixture, tests, and documentation enforce the same transport contract.

Published packages:

  • @relykit/oidc@0.1.1
  • @relykit/nuxt@0.1.1

Both packages include npm provenance. Publication run 29740930280 consumed the exact artifacts from approved dry run 29707591055 without repacking.

SHA-256:

  • relykit-oidc-0.1.1.tgz: 7770dbfc3b9618c1e4c12dabdf975dfb7b73fff14a3c944a8ceffe558da8645f
  • relykit-nuxt-0.1.1.tgz: 967f60f267a6cc77b5fe14843db7277c0598fbb80fa777b7b2fba23f4b14b09a

RelyKit 0.1.0

Choose a tag to compare

@bi0nd0 bi0nd0 released this 19 Jul 17:38
d28ded6

RelyKit 0.1.0 is the first stable coordinated release of @relykit/oidc and @relykit/nuxt.

Highlights:

  • provider-neutral OAuth 2.1/OpenID Connect integration for Nuxt applications
  • structured RP-Initiated Logout requests with form-POST ID-token transport
  • complete two-session logout lifecycle with separately sealed evidence, one-time state, callback verification, replay rejection, and safe provider-failure retry
  • exact coordinated dependency between the Nuxt and OIDC packages
  • public npm packages published with SLSA provenance through the protected npm environment

Release integrity:

  • approved dry run: 29697045636
  • publication run: 29697114980
  • @relykit/oidc SHA-256: 1666dc26a84e1fd36010f5b87e4a968b06e6b36a359308d4ea84a20cd7152541
  • @relykit/nuxt SHA-256: 05c494cc76640b0f14ecd0dc133621edae1a29ae256f5bf4c09b98184191776d

The attached tarballs are byte-for-byte identical to the artifacts published to npm. Verify them with the attached SHA256SUMS file.