ark-oauth-client-node 2.2.1 → 2.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/CHANGELOG.md +20 -0
  2. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -1,5 +1,25 @@
1
1
  # Changelog
2
2
 
3
+ ## 2.3.0
4
+
5
+ No change to this package. It has the same code, API and options as 2.2.1 and is published at the
6
+ family's version. In this release the .NET packages, `Ark.oAuth.Oidc` and `Ark.oAuth.Client`, move
7
+ to .NET 10 and EF Core 10.
8
+
9
+ There is nothing to do when you upgrade. The provider's endpoints, tokens and discovery document are
10
+ the same in 2.3.0 as in 2.2.x. This client therefore behaves the same against a 2.2.x provider and a
11
+ 2.3.0 one, and you can upgrade the two in either order. The requirements are unchanged: Node 20 or
12
+ later, ESM, and no runtime dependencies. The built-in access-denied page names
13
+ `ark-oauth-client-node 2.3.0` in its footer.
14
+
15
+ If you are still on the old package name, `ark-oauth-client` (up to 2.1.8), the move to this name is
16
+ described under 2.2.0 below.
17
+
18
+ ## 2.2.1
19
+
20
+ 2.2.0 republished through the repository's release workflow. The published files differ from 2.2.0
21
+ only in the version number.
22
+
3
23
  ## 2.2.0
4
24
 
5
25
  **Renamed to `ark-oauth-client-node`.** Up to 2.1.8 this package was published as
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "ark-oauth-client-node",
3
- "version": "2.2.1",
3
+ "version": "2.3.0",
4
4
  "description": "The OAuth 2.1 / OpenID Connect client for Node.js applications, built for Ark.oAuth.Oidc. Authorization code + PKCE with state, nonce, iss and at_hash checks, JWKS rotation, silent refresh, client credentials, the device grant, PAR, introspection, revocation, dynamic client registration and RP-initiated logout \u2014 plus Express/Connect middleware for interactive sign-in, account switching on a shared browser, and protecting an API. No runtime dependencies.",
5
5
  "keywords": [
6
6
  "oauth",