Tags

Tags give the ability to mark specific points in history as being important

  • v1.0.5

    protected
    8c51bce9 · Bump version to 1.0.5 ·
    Release: v1.0.5 
    v1.0.5

- Updated dependencies (m3api-rest v0.2.0).

  • v1.0.4

    protected
    d27e8f19 · Bump version to 1.0.4 ·
    Release: v1.0.4 
    v1.0.4

- Fixed the automatic handling of expired access tokens (including
  retrying the request) on Wikimedia wikis, which had been broken due to
  [T419034][].
- Updated dependencies, including m3api v1.1.0.

[T419034]: https://phabricator.wikimedia.org/T419034

  • v1.0.3

    protected
    92f4c0d7 · Bump version to 1.0.3 ·
    Release: v1.0.3 
    v1.0.3

- Internal improvements, including using [m3api-rest][]. There should be
  no impact on users of the package.
- Updated dependencies.

[m3api-rest]: https://www.npmjs.com/package/m3api-rest

  • v1.0.2

    protected
    1cdfe9ae · Bump version to 1.0.2 ·
    Release: v1.0.2 
    v1.0.2

- m3api-oauth2 documentation is now published at
  <https://doc.wikimedia.org/m3api/m3api-oauth2/>.
  (The previous location, GitHub Pages, is kept for now,
  but will probably be changed to a redirect sooner or later.)
- Updated dependencies.

  • v1.0.1

    protected
    e8106060 · Bump version to 1.0.1 ·
    Release: v1.0.1 
    v1.0.1

Migration to Wikimedia GitLab.

- m3api hosting migrated from GitHub to Wikimedia GitLab. If you use the
  library via npm, nothing should change for you, but if you cloned the
  repository from GitHub, please change the remote to
  <https://gitlab.wikimedia.org/repos/m3api/m3api-oauth2.git>.
- Updated dependencies.

  • v1.0.0

    protected
    d8b02692 · Bump version to 1.0.0 ·
    Release: v1.0.0 
    v1.0.0

- First stable release 🎉
- Require m3api v1.0.0.
- Updated dependencies.

  • v0.3.4

    protected
    8a08efce · Bump version to 0.3.4 ·
    Release: v0.3.4 
    v0.3.4

- Added support for the new `accessToken` option in m3api.
- Declared compatibility with m3api v0.9.0. (v0.8.x remains supported.)
- Updated dependencies.

  • v0.3.3

    protected
    3896f698 · Bump version to 0.3.3 ·
    Release: v0.3.3 
    v0.3.3

Better state management.

- Two changes are meant to make it easier to use m3api-oauth2 correctly:
  A new `isCompleteOAuthSession()` function is available, and
  `initOAuthSession()` is now idempotent. This should make it
  unnecessary for users of the library to track or deduce the current
  state of the authorization flow (i.e., whether `initOAuthSession()`
  was already called, and whether `completeOAuthSession()` was already
  called). If `isCompleteOAuthSession()` returns `false`, the user is
  not logged yet – call `initOAuthSession()` to get the authorization
  URL (it doesn’t matter if it was already called or not); if
  `isCompleteOAuthSession()` returns `true`, the user is logged in.
- Updated dependencies.

  • v0.3.2

    protected
    7dbd350f · Bump version to 0.3.2 ·
    Release: v0.3.2 
    v0.3.2

- The callback URL passed into `completeOAuthSession()` may now be a
  relative URL.
- Improved error handling in `completeOAuthSession()`.
- Updated dependencies.

  • v0.3.1

    protected
    e707fc04 · Revert "npm update" ·
    Release: v0.3.1 
    v0.3.1

Fix for new MediaWiki versions.

- Updated m3api requirement to the latest version (0.8.3) – versions
  0.8.0-0.8.2 no longer work against Wikimedia production since mid-June
  2024 (see issue #3).
- Updated dependencies.

  • v0.3.0

    protected
    c42688a0 · Bump version to 0.3.0 ·
    Release: v0.3.0 
    v0.3.0

- BREAKING CHANGE: m3api-oauth2 now requires at least Node.js version
  18.2.0, up from Node 12.22.0 or Node 14.17.0 previously. As part of
  this, the `m3api-oauth2/requireCrypto` request option has been
  removed, as we no longer support any platform where the Web Crypto API
  is not available: it is now always used unconditionally.
- Updated dependencies.

  • v0.2.0

    protected
    7538a951 · Bump version to 0.2.0 ·
    Release: v0.2.0 
    v0.2.0

Auto-refresh \o/

- The access token is now refreshed automatically; it is no longer
  necessary to call `refreshOAuthSession()` by hand, and sessions should
  remain usable indefinitely.
- Updated dependencies.

  • v0.1.1

    protected
    489f37f8 · Bump version to 0.1.1 ·
    Release: v0.1.1 
    v0.1.1

No code changes from v0.1.0,
just a fix to the GitHub Actions workflow pushing the release to npm.
(v0.1.0 could not be pushed to npm, unfortunately.)

To reiterate, v0.1.0 and v0.1.1 include:

- The `OAuthClient` class and `initOAuthSession()` and
  `completeOAuthSession()` functions, to perform the OAuth 2.0
  authorization code flow.
- The `refreshOAuthSession()` function, to perform the refresh flow
  (albeit not yet automatically).
- The `serializeOAuthSession()` and `deserializeOAuthSession()`
  functions, to serialize the OAuth state of a session between requests.
- PKCE support, for non-confidential clients without a client secret.

  • v0.1.0

    protected
    b8e2c8db · Add 0.1.0 release date to CHANGES.md ·
    Release: v0.1.0 
    v0.1.0

Initial release, including:

- The `OAuthClient` class and `initOAuthSession()` and
  `completeOAuthSession()` functions, to perform the OAuth 2.0
  authorization code flow.
- The `refreshOAuthSession()` function, to perform the refresh flow
  (albeit not yet automatically).
- The `serializeOAuthSession()` and `deserializeOAuthSession()`
  functions, to serialize the OAuth state of a session between requests.
- PKCE support, for non-confidential clients without a client secret.