Demand is heating up for Migration API

We are getting more and more feedback from our beta users, and fielding a higher amount of requests for our 15 rotating api keys than ever before!

This is great news, as we are starting to get the first signals that new repos and new business will be created thanks to this new feature!

Updates from last week:

Have a backend implementation of permanent token by end of week 😐

Fix small bugs from migration release

• We fixed the empty state screen, showing the publish button as inactive if no documents have been added yet
• We made sure the migration release was no longer being displayed in the publish workflow of the PageBuilder.

Improvements based on Migration API beta user feedback:

• Improved UID error validation message on update requests to the Migration API
• Removed validation errors for empty link fields on update requests
• On the Migration API Beta cluster only, the back button in the legacy editor was unresponsive, this is now fixed.

Goal for this week:

Build the new core api endpoint to move update requests from draft and published documents to migration releases

Right now, any update (PUT) requests from the Migration API for documents that are not already in the migration release are generating draft documents in the document list.

Bulk updates, of links for instance, are a common need when doing large migrations. So we want to make sure users who want to bulk update links or other content in their repository can take advantage of one-click publishing in a migration release.

We plan to be ready for testing this addition to migration releases by the end of the week.