Skip to content

ci: bump plugin-actions/wait-for-grafana to v1.0.4#2734

Open
mckn wants to merge 1 commit into
mainfrom
mckn/bump-wait-for-grafana-v1-0-4
Open

ci: bump plugin-actions/wait-for-grafana to v1.0.4#2734
mckn wants to merge 1 commit into
mainfrom
mckn/bump-wait-for-grafana-v1-0-4

Conversation

@mckn

@mckn mckn commented Jun 22, 2026

Copy link
Copy Markdown
Collaborator

What

Bumps the SHA-pinned grafana/plugin-actions/wait-for-grafana action across this repo's workflows to wait-for-grafana/v1.0.4 (686ff64):

  • .github/workflows/ci.yml (4 occurrences) — v1.0.1 → v1.0.4
  • .github/workflows/playwright.yml — v1.0.3 → v1.0.4
  • .github/workflows/playwright-nightly.yml — v1.0.1 → v1.0.4

Why

Keep the monorepo CI on the latest wait-for-grafana. No input/output changes.

🤖 Generated with Claude Code

Update the SHA-pinned wait-for-grafana action across the repo workflows
to wait-for-grafana/v1.0.4:

- ci.yml (4 occurrences): v1.0.1 -> v1.0.4
- playwright.yml: v1.0.3 -> v1.0.4
- playwright-nightly.yml: v1.0.1 -> v1.0.4

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@mckn mckn requested review from a team as code owners June 22, 2026 10:10
@mckn mckn requested review from Ukochka, academo and sunker June 22, 2026 10:10
@mckn mckn requested review from eledobleefe and jackw June 22, 2026 10:10
@github-project-automation github-project-automation Bot moved this from 📬 Triage to 🔬 In review in Grafana Catalog Team Jun 22, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Playwright test results

Image Name Version Result Report
grafana-enterprise nightly View report
grafana-enterprise dev-preview-react19
grafana-enterprise 13.0.2
grafana-enterprise 11.0.11
grafana-enterprise 9.3.16
grafana-enterprise 8.5.27
Troubleshooting

404 when clicking on View report

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:

  1. Go to the Settings tab of your repository.
  2. In the left-hand sidebar, click on Pages.
  3. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 🔬 In review

Development

Successfully merging this pull request may close these issues.

2 participants