New m3api-oauth2 release! (m3api-oauth2 is still an m3api extension package to authenticate users using OAuth 2.)

This just declares compatibility with the newly released m3api-rest v0.2.0, nothing special 

https://gitlab.wikimedia.org/repos/m3api/m3api-oauth2/-/releases/v1.0.5

#m3api #MediaWiki

v1.0.5 · repos / m3api / m3api-oauth2 · GitLab

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

GitLab

New m3api-rest release! (m3api-rest is still an m3api extension package to use the MediaWiki REST API.)

THIS is what this has all been building up to! m3api-rest now supports the following:
• request methods: GET, POST, PUT, DELETE, PATCH
• request body content types: JSON, URLSearchParams, FormData
• response body content types: JSON, (plain) text, HTML

resulting in 17 instead of 4 exported functions, a 325% increase!! :D

https://gitlab.wikimedia.org/repos/m3api/m3api-rest/-/releases/v0.2.0

#m3api #MediaWiki

v0.2.0 · repos / m3api / m3api-rest · GitLab

v0.2.0 Major functionality update: beyond getJson() and postForJson(), m3api-rest now supports the following: request methods: ...

GitLab

New m3api-oauth2 release! (m3api-oauth2 is an m3api extension package to authenticate users using OAuth 2.)

This likewise updates the library to work with latest m3api, and also introduces a new HTTP-level error handler, to handle the fact that Wikimedia infrastructure now responds differently to requests with expired access tokens, which broke our previous automatic refresh functionality 😔

https://gitlab.wikimedia.org/repos/m3api/m3api-oauth2/-/releases/v1.0.4

#m3api #MediaWiki

v1.0.4 · repos / m3api / m3api-oauth2 · GitLab

v1.0.4 Fixed the automatic handling of expired access tokens (including retrying the request) on Wikimedia wikis, which had been broken due to

GitLab

New m3api-rest release! (m3api-rest is an m3api extension package to use the MediaWiki REST API.)

From an external point of view, this is just a patch version bump to make the library compatible with the latest m3api. (Internally, this of course meant quite a few changes, as the m3api maintainer changed the whole network interface this library was using, that thoughtless prick.) The promised new features will come a bit later 

https://gitlab.wikimedia.org/repos/m3api/m3api-rest/-/releases/v0.1.1

#m3api #MediaWiki

v0.1.1 · repos / m3api / m3api-rest · GitLab

v0.1.1 Updated the library for the new network interface of m3api v1.1.0, so that it can be used together with that version. (This also...

GitLab

New m3api release! (m3api is a JavaScript library to use the MediaWiki Action API.)

This version overhauls the internal network interface, which will unlock many new features in the m3api-rest extension package, and introduces a new internal option that will allow m3api-oauth2 to fix an issue with automatic retrying of requests with expired access tokens. (Stay tuned for new releases of those packages in the coming hours )

https://gitlab.wikimedia.org/repos/m3api/m3api/-/releases/v1.1.0

#m3api #MediaWiki

v1.1.0 · repos / m3api / m3api · GitLab

v1.1.0 Internal Breaking Change: The internal network interface has been replaced. Instead of session.internalGet() and session.internalPost(), there is now a single

GitLab

new #m3api release! (m3api is a JavaScript library to use the MediaWiki action API :3)

just two changes:
• a minor change to the handling of responses with Retry-After headers which should hopefully be useful especially when targeting Wikimedia wikis
• a new declaration that changing the supported Node.js versions is not considered a breaking change (and what to do if you need support for a specific Node.js version)

https://gitlab.wikimedia.org/repos/m3api/m3api/-/releases/v1.0.4

v1.0.4 · repos / m3api / m3api · GitLab

v1.0.4 Improved handling of retry-after responses (especially ones with HTTP status 429 Too Many Requests). README.md § Stability has...

GitLab

unfinished thought: it would be quite good to have something like the Toolforge Abandoned Tool policy (https://wikitech.wikimedia.org/wiki/Help:Toolforge/Abandoned_tool_policy) for non-tool Wikimedia code, such as libraries (e.g. #m3api) or applications (e.g. Pattypan?)

this could be a step towards “Off-the-shelf governance models for small FOSS projects” (@pintoch, https://antonin.delpeuch.eu/posts/off-the-shelf-governance-models-for-small-foss-projects/) – if a codebase opts into it (README.md?), there would be an established process for adopting it if the maintainer goes inactive

#Wikimedia #Toolforge

Help:Toolforge/Abandoned tool policy - Wikitech

and, after some CI troubles (https://phabricator.wikimedia.org/T414864), m3api-oauth2 v1.0.3 is out, now using the new m3api-rest package (see above) internally! \o/

https://gitlab.wikimedia.org/repos/m3api/m3api-oauth2/-/releases/v1.0.3

#m3api

T414864 Unblock running tests against Beta Cluster from Digital Ocean GitLab CI runners

Please unblock access from these IPs to the Beta Cluster:

Phabricator

to kick off the new year, here’s a new m3api extension package! m3api-rest lets you make some requests to the MediaWiki REST API :)

it’s only v0.1.0 and it’s quite limited, so probably you shouldn’t look at it too closely yet ;) more powerful versions should come soonish and then it’ll be more useful, with support for more request methods and request+response content types ^^

https://www.npmjs.com/package/m3api-rest
https://doc.wikimedia.org/m3api/m3api-rest/v0.1.0/

#m3api

I’m planning to create a library that makes it easier to use the MediaWiki REST API from applications which already use m3api to interact with the Action API; input welcome here, as I’m not actually very familiar with the REST API: https://phabricator.wikimedia.org/T411325

#m3api #MediaWiki

T411325 Introduce m3api extension package to use the REST API (m3api-rest)

While m3api is mainly focused on the Action API, and to my knowledge the REST API doesn’t have a lot of “common” functionality…

Phabricator