[FEATURE] Add plugin versioning support + dashboard lock mode by Gladorme · Pull Request #243 · perses/shared

Gladorme · 2026-08-20T16:01:50Z

Description

The goal of this PR is to improve the handling of plugin versioning in dashboard:

show plugin version in panel type selector if there is more than one version available
"lock" dashboard feature

What is doing the lock mode?
Lock will enforce versioning on all plugins. It will use latest version installed. When a new version is available, it will show a button to update, with a nice diff based on the first panel using the plugin (only for panel plugin). If the plugin version pinned is no longer available, it will show a error.

Blocked, need spec release v0.3.0-beta.4 fixed (token expired, need @Nexucis back :p) and need perses/plugins#773 too

Screenshots

Checklist

Pull request has a descriptive title and context useful to a reviewer.
Pull request title follows the [<catalog_entry>] <commit message> naming convention using one of the
following catalog_entry values: FEATURE, ENHANCEMENT, BUGFIX, BREAKINGCHANGE, DOC,IGNORE.
All commits have DCO signoffs.

UI Changes

Changes that impact the UI include screenshots and/or screencasts of the relevant changes.
Code follows the UI guidelines.
E2E tests are stable and unlikely to be flaky.
See e2e docs for more details. Common issues include:
- Is the data inconsistent? You need to mock API requests.
- Does the time change? You need to use consistent time values or mock time utilities.
- Does it have loading states? You need to wait for loading to complete.

shahrokni · 2026-08-21T10:53:06Z

I see this PR is still in draft mode. Are you still working on this?

Gladorme · 2026-08-21T12:40:27Z

I see this PR is still in draft mode. Are you still working on this?

No, the PR is ready, but it's depending on other PRs, so can't be merged

Signed-off-by: Guillaume LADORME <Gladorme@users.noreply.github.com>

Signed-off-by: Guillaume LADORME <gladorme@gmail.com>

jgbernalp · 2026-08-31T08:34:33Z

                {isLinksEnabled && <EditDashboardLinksButton />}
                <AddPanelButton />
                <AddGroupButton />
+                <UpdatePluginsButton />


It seems this button also locks the version to the latest one. Should the update options allow to "unset" the version so always the latest is used?

Well to set "unset", the best would be to use "Unlock" button. But it make me think it's better to enable this button/feature only if lock mode is available.

jgbernalp · 2026-08-31T08:35:35Z

                {isLinksEnabled && <EditDashboardLinksButton />}
                <AddPanelButton />
                <AddGroupButton />
+                <UpdatePluginsButton />


Admins might want to prevent unintended updates, I think we should add configuration so this can be disabled/hidden

Like in previous comment, I will make this feature only available if lock mode is available. If admin don't want to allow user to upgrade version, it will need a change in back, because user can easily change version json directly

In embedded usage, people can enable or disable the button separately (I added a new condition)

Signed-off-by: Guillaume LADORME <Gladorme@users.noreply.github.com>

jgbernalp · 2026-09-02T14:45:15Z

+      return optionValue;
+    }
+    // The definition is not pinned (or is pinned to something we don't list): fall back to the first entry of that
+    // plugin kind, which is the one that will actually be used, so the Select has a matching value.


The first option in the dropdown might not be the latest version installed, which is the one it should fallback if there is no version installed. I wonder if we should flag the current latest inside the dropdown, I see a problem when you want to create a dashboard that uses the latest plugin version. If we just allow pinned versions from the dropdown this wont be possible.

My main concern is that you pin a plugin version in your dashboard, then update perses and then the dropdown will select that version, but your dashboard still continues to be pinned to the older version.

jgbernalp · 2026-09-02T14:53:44Z

+  /**
+   * When true, offers the button that locks/unlocks the dashboard, i.e. pins every plugin it uses to an exact version.
+   * It only makes the action available: whether the dashboard is actually locked is derived from its plugin
+   * definitions. Not available by default. Plugin versioning itself is always on: the button that updates
+   * already-pinned plugins is shown regardless of this flag.
+   */


I got lost on this comment, it says a lot of things but it seems contradictory in the button that updates already-pinned plugins is shown regardless of this flag. as the button is gated behind the isUpdateButtonAvailable.

Gladorme changed the title ~~Versioning lock~~ [FEATURE] Add plugin versioning + dashboard lock mode Aug 20, 2026

Gladorme changed the title ~~[FEATURE] Add plugin versioning + dashboard lock mode~~ [FEATURE] Add plugin versioning support + dashboard lock mode Aug 20, 2026

Gladorme mentioned this pull request Aug 21, 2026

[FEATURE] Add dashboard lock mode perses/perses#4370

Draft

6 tasks

shahrokni self-requested a review August 21, 2026 10:52

Gladorme force-pushed the versioning-lock branch from d101a63 to 7802d79 Compare August 26, 2026 15:44

jgbernalp reviewed Aug 27, 2026

View reviewed changes

Comment thread dashboards/src/components/GridLayout/GridItemContent.tsx Outdated