Update script using create-plugin update tool #290
Merged
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
Ukochka
requested review from
mckn,
wbrowne,
andresmgot and
xnyo
and removed request for
a team
academo
approved these changes
May 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
History:
There was a script which @academo wrote to update grafana packages. It took desired grafana version and updated specific packages to this version.
Work:
While fixing problems for mac OS I added some improvements to check first if the current version is newer than target version and leave it as it is to avoid downgrading
Latest updates:
But we decide to use npx create-plugin@latest update to update plugins from now on, because in the future we want to make it automatically.
So this PR is a first step to do it. After there will be several PRs about updates themself