Update: Trigger content migrations on plugin update

[taylortom]

Update

• updatePlugin() now captures before/after plugin versions via readFrameworkPluginVersions
• Finds courses using the updated plugin and calls framework.migrateCourses() to run content migrations

Fix

• Re-register plugin schemas after a JsonSchema registry reset — pluginSchemas now stores {name: {anchor: filePath}} so plugin extensions can be re-registered via the new JsonSchemaModule.registerSchemasHook tap. Prevents MISSING_SCHEMA errors when the registry is reset (e.g. T10.3 plugin uninstall/reset cycles)

Testing

• Depends on New: Run adapt-migrations directly for all trigger points adapt-authoring-adaptframework#174 for the migrateCourses() method and readFrameworkPluginVersions export
• Replaces the grunt-based approach from New: migration scripts to run on plugin update (fixes #28) #29

[github-actions]

🎉 This PR is included in version 1.7.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀