fix: revert plugin-directory input in e2e-versions #121
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-project-automation
bot
moved this to 📬 Triage
in Plugins Platform / Grafana Community
sunker
changed the title
xnyo
approved these changes
Sep 26, 2025
github-project-automation
bot
moved this from 📬 Triage
to 🔬 In review
in Plugins Platform / Grafana Community
Contributor
|
Reverts #75 |
github-project-automation
bot
moved this from 🔬 In review
to 🚀 Shipped
in Plugins Platform / Grafana Community
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR reverts the recently introduced
plugin-directoryfeature. The change was not fully propagated in the previous release becauseindex.jswas not rebuilt, which meant downstream users of this Action only received the update starting with version 1.1.1. Since this has caused unintended issues, the safest step for now is to roll back the feature.After the recent refactoring in this Action, the bundling may not be necessary anymore. I'll handle that in a follow up pr.