You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The corresponding Grafana change didn't make it to the 12.4 release as intended.
rrc whereis pr 117817
Commit is found in:
ENVIRONMENT / RELEASE CHANNEL CURRENT VERSION
instant 13.0.0-22350019450
fast 13.0.0-22184160961 --> 13.0.0-22326976726 **
Hello! 👋 This repository uses Auto for releasing packages using PR labels.
✨ This PR can be merged and will trigger a new patch release. NOTE: When merging a PR with the release label please avoid merging another PR. For further information see here.
By default, the deploy-report-pages Action deploys reports to the gh-pages branch. However, you need to take an extra step to ensure that GitHub Pages can build and serve the site from this branch. To do so:
Go to the Settings tab of your repository.
In the left-hand sidebar, click on Pages.
Under Source, select Deploy from a branch, then choose the gh-pages branch.
This action needs to be completed manually in order for your GitHub Pages site to be built and accessible from the gh-pages branch. Once configured, GitHub will automatically build and serve the site whenever new reports are deployed.
Ah okay, so same problem as described in this PR description surfaced in the react19 preview image. The solution is to sync the react19 branch with main and publish a new image. I'll look into this,
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
patchIncrement the patch version when mergedreleaseCreate a release when this pr is mergedreleasedThis issue/pull request has been released.
4 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.
sunker
requested review from
Ukochka and
Copilot
and removed request for
Copilot
github-project-automation
bot
moved this from 📬 Triage
to 🔬 In review
in Grafana Catalog Team
grafana-plugins-platform-bot
bot
added
the
released
What this PR does / why we need it:
The corresponding Grafana change didn't make it to the 12.4 release as intended.
This is causing issues here for example: #2478
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
📦 Published PR as canary version:
Canary Versions✨ Test out this PR locally via:
npm install @grafana/plugin-docs-cli@0.0.3-canary.2479.22359816249.0 npm install @grafana/plugin-docs-parser@0.0.2-canary.2479.22359816249.0 npm install @grafana/plugin-e2e@3.3.3-canary.2479.22359816249.0 # or yarn add @grafana/plugin-docs-cli@0.0.3-canary.2479.22359816249.0 yarn add @grafana/plugin-docs-parser@0.0.2-canary.2479.22359816249.0 yarn add @grafana/plugin-e2e@3.3.3-canary.2479.22359816249.0