@grafana/create-plugin 6.3.0-canary.2320.19632326797.0 → 6.3.0-canary.2320.19638409321.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@grafana/create-plugin",
-  "version": "6.3.0-canary.2320.19632326797.0",
+  "version": "6.3.0-canary.2320.19638409321.0",
   "repository": {
     "directory": "packages/create-plugin",
     "url": "https://github.com/grafana/plugin-tools"
@@ -61,5 +61,5 @@
   "engines": {
     "node": ">=20"
   },
-  "gitHead": "5b46b985dfd18a905e572b69ca71c8f5148a8043"
+  "gitHead": "a85de24ae42ffcfee01d3c1b039257f5b2fd10d2"
 }

package/src/codemods/AGENTS.md

@@ -5,17 +5,24 @@ This guide provides specific instructions for working with migrations and additi
 ## Agent Behavior
 
 - Refer to current migrations and additions typescript files found in @./additions/scripts and @./migrations/scripts
-- When creating a new migration add it to the exported migrations object in @./migrations/migrations.ts
 - Always refer to @./context.ts to know what methods are available on the context class
 - Always check for file existence using the @./context.ts class before attempting to do anything with it
 - Never write files with any 3rd party npm library. Use the context for all file operations
-- Always return the context for the next migration
+- Always return the context for the next migration/addition
 - Test thoroughly using the provided utils in @./test-utils.ts where necessary
+- Never attempt to read or write files outside the current working directory
+
+## Migrations
+
+Migrations are automatically run during `create-plugin update` to keep plugins compatible with newer versions of the tooling. They are forced upon developers to ensure compatibility and are versioned based on the create-plugin version. Migrations primarily target configuration files or files that are scaffolded by create-plugin.
+
+### Migration Behavior
+
+- When creating a new migration add it to the exported migrations object in @./migrations/migrations.ts
 - Each migration must be idempotent and must include a test case that uses the `.toBeIdempotent` custom matcher found in @../../vitest.setup.ts
 - Keep migrations focused on one task
-- Never attempt to read or write files outside the current working directory
 
-## Naming Conventions
+### Migration Naming Conventions
 
 - Each migration lives under @./migrations/scripts
 - Migration filenames follow the format: `NNN-migration-title` where migration-title is, at the most, a three word summary of what the migration does and NNN is the next number in sequence based on the current file name in @./migrations/scripts
@@ -23,3 +30,16 @@ This guide provides specific instructions for working with migrations and additi
   - `NNN-migration-title.ts` - main migration logic
   - `NNN-migration-title.test.ts` - migration logic tests
 - Each migration should export a default function named "migrate"
+
+## Additions
+
+Additions are optional features that developers choose to add via `create-plugin add`. They are not versioned and can be run at any time to enhance a plugin with new capabilities.
+
+### Addition Behavior
+
+- Additions add new features or capabilities to a plugin (e.g., i18n support, testing frameworks, etc.)
+- Each addition must be idempotent - it should be safe to run multiple times
+- Always use defensive programming: check if features already exist before adding them
+- Use `additionsDebug()` for logging to help with troubleshooting
+- If the addition accepts user input, export a `schema` object using `valibot` for input validation
+- Each addition should export a default function that takes `(context: Context, options?: T)` and returns `Context`

package/templates/panel/src/plugin.json

@@ -19,7 +19,7 @@
     "updated": "%TODAY%"
   },
   "dependencies": {
-    "grafanaDependency": ">=10.4.0",
+    "grafanaDependency": ">=11.5.0",
     "plugins": []
   }
 }