From 49ef18b2b700a8226d671059cff507ae4566a0ce Mon Sep 17 00:00:00 2001 From: "Grot (@grafanabot)" <43478413+grafanabot@users.noreply.github.com> Date: Mon, 6 Mar 2023 03:57:18 -0500 Subject: [PATCH] [v9.4.x] Docs: Adding angular support deprecation to our plugin submission FAQ (#64201) Docs: Adding angular support deprecation to our plugin submission FAQ (#64006) Adding angular support deprecation to our faq (cherry picked from commit 43e281271b8b365273cce07b54c27835fd2eb9cd) Co-authored-by: Timur Olzhabayev --- docs/sources/developers/plugins/publish-a-plugin.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/sources/developers/plugins/publish-a-plugin.md b/docs/sources/developers/plugins/publish-a-plugin.md index 2896896df02..4e98489be36 100644 --- a/docs/sources/developers/plugins/publish-a-plugin.md +++ b/docs/sources/developers/plugins/publish-a-plugin.md @@ -121,6 +121,10 @@ To speed up the time it takes to review your plugin: - The official method for distributing Grafana plugins is through the Grafana Catalog. Alternative methods, such as installing private or development plugins on local Grafana instances, are available as per the guidelines provided in [this guide](https://grafana.com/docs/grafana/latest/administration/plugin-management/#install-plugin-on-local-grafana). +**Can I still use Angular for my plugin?** + +- No. We will not accept any new plugin submissions written in angular. Please take a look at our [angular support deprecation documentation](https://grafana.com/docs/grafana/latest/developers/angular_deprecation/). + ## Publishing your plugin for the first time **Do plugin signatures expire?**