# Create Plugin v6 released

**URL:** <https://community.grafana.com/t/create-plugin-v6-released/158731>\
**Category:** Announcements\
**Tags:** plugins\
**Created:** [October 22, 2025, 7:00am UTC](https://community.grafana.com/t/create-plugin-v6-released/158731 "2025-10-22T07:00:49Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jackwestbrook](https://sea2.discourse-cdn.com/grafana/user_avatar/community.grafana.com/jackwestbrook/32/21296_2.png) [@jackwestbrook](https://community.grafana.com/u/jackwestbrook)\
**Post date:** [October 22, 2025, 7:00am UTC](https://community.grafana.com/t/create-plugin-v6-released/158731/1 "2025-10-22T07:00:49Z")

</div>

**What’s new?**  
Create Plugin is changing how it updates plugins. Starting from 6.0.0, we’re introducing **updates as migrations** to the `@grafana/create-plugin update` command. We’ve never been happy with the update command implementation and had several related issues in our backlog. The legacy approach would often result in unwanted changes, failed dependency installs, and large PRs that were hard to review.  
The new update approach aims to solve these issues by running a series of migrations that each focus on a single task to bring your plugin up to date. This should make for a more user friendly experience with better logging, option to git commit each successful migration, better error handling and rollback support should something go wrong during a migration. ([Docs link](https://grafana.com/developers/plugin-tools/how-to-guides/updating-a-plugin).)

If you are using the shared [create-plugin-update](https://github.com/grafana/plugin-actions/tree/main/create-plugin-update#workflow-example) github workflow to keep your plugin updated via CI we recommend updating the version of the shared workflow to `v.1.1.0` which provides support for the new `--commit` arg.

**Breaking Changes Alert!**  
`create-plugin update` now only update dependencies if a migration requires it. This should generally make for smaller PRs, less noise, and stop competing with other dependency update bots. If you’re not already using them, use either [dependabot](https://docs.github.com/en/code-security/getting-started/dependabot-quickstart-guide) or [renovatebot](https://docs.renovatebot.com/) to keep your dependencies up to date.