
Why Publish Plugin Versions?
Publishing plugin versions is crucial for maintaining control and stability in your Amplication environment. It allows you to:Establish Stable Releases
Control Updates and Changes
Step 1: Add a New Plugin Version in Amplication
Next, you’ll add a new version entry for your plugin within the Amplication Platform Console. This version will correspond to a specific tag in your Git repository in the next step.Navigate to Private Plugins
Scroll to 'Add New Version'
Click 'Add Version'
Note the Version Number

Add a new version for your plugin in the Platform Console.
Step 2: Tag Your Git Repository with the Version
Now, you need to tag your plugin’s Git repository to associate a specific commit with the version you just added in Amplication. Amplication uses these tags to identify plugin versions during code generation.Navigate to Your Plugin's Local Repository
Create a Git Tag
git tag
command to create a tag. The tag format must be: your-plugin-id@version-number
. Replace your-plugin-id
with your actual Plugin ID (the folder name of your plugin) and version-number
with the version you noted in the previous step (e.g., 0.1.0
).Push the Tag to Your Remote Repository
git push
command, specifying the tag name.your-plugin-id@version-number
) and push the tag to your remote repository. Amplication relies on these tags to correctly identify and fetch the plugin code for each version.Step 3: Publish the Plugin Version in Amplication
Finally, you need to publish the version through the Amplication Platform Console to make it officially available.Go to Platform Console Changes
Click 'Publish New Version'
Add an Optional Version Message
Click 'Publish'

Publish your changes to make the new plugin version live.
Step 4: Disable Dev Versions (Optional)
To absolutely make sure you are publishing a stable version of your plugin, you can optionally disable Dev Versions, so that resources can’t select the @dev version. This ensures that you are publishing a stable version based on a specific point in your codebase, not the potentially changing code in your development branch.Navigate to Private Plugins
Select Your Plugin
Disable Dev Version Toggle

Disable Dev Versions before publishing.

Add your newly published private plugin to a resource or template.