Agency Update - M2M fix for Permanent Tokens

Updates from last week:

❌

Release a fix for performance issues around publishing of migration releases

We made progress last week thanks to the support of Seb, but we are not yet at the point of being able to merge the PR. As Amaury is off this week, we do not expect this to be done until the week of Feb. 26 at the earliest.

✅

Update integration tests on Migration API (and permanent token error message)

We released the error message letting users who tried to make requests with permanent tokens know that this was currently unavailable early last week, as well as merged the improved test coverage.

Goals for the next week:

Release M2M token fix for Migration API and Asset API

We released a mid-term fix that allows permanent tokens to work with the Migration API and Asset API again after the introduction of a user requirement on Asset API side. It works as follows:

Documents created/updated via the Migration API with a permanent token use the repository owner as the user that did this action.
Media created/updated via the Asset API does not show a user name at all. This was possible due to a previous functionality already implemented there for migrating to the new media library.

Continue investigation into work on bulk actions in order to expand limit on Migration Release above 1k

We are resuming an investigation started nearly a month ago around improving performance for bulk actions with the end goal of expanding the migration release limit to over 1k. Once completed, it will also enable PageBuilder team to expand the general limit on bulk actions in the document list significantly above 200 if they choose to do so.