Subject of the issue/enhancement/features
Currently each migration script requires the latest plugin version for multiple purposes, inputting this manually could cause issues given when we're creating the script we don't know what the version number will be on release. Idea is to use semantic-release-replace-plugin to replace @@Version (in the script), with the release version, as discussed some modifications to adapt-migrations needed to replace @@Version when run.