Skip to content

ci: bump plugin-actions/e2e-version to v3.0.1#2733

Open
mckn wants to merge 2 commits into
mainfrom
mckn/bump-e2e-version-v3
Open

ci: bump plugin-actions/e2e-version to v3.0.1#2733
mckn wants to merge 2 commits into
mainfrom
mckn/bump-e2e-version-v3

Conversation

@mckn

@mckn mckn commented Jun 22, 2026

Copy link
Copy Markdown
Collaborator

What

Bumps the SHA-pinned grafana/plugin-actions/e2e-version action in this repo's own workflows to e2e-version/v3.0.1 (304ed38):

  • .github/workflows/playwright.yml — v2.0.0 → v3.0.1
  • .github/workflows/playwright-nightly.yml — v1.2.0 → v3.0.1

Why

Keep the monorepo CI on the latest e2e-version.

Breaking change handled

v3's only breaking change is removing the broken react19 preview image from the test matrix (#249) — which also removed the skip-grafana-react-19-preview-image input. playwright-nightly.yml previously set that input, so this PR drops the now non-existent input. All other inputs (version-resolver-type, grafana-dependency, skip-grafana-dev-image, limit) are unchanged.

🤖 Generated with Claude Code

Update the SHA-pinned e2e-version action in playwright.yml (v2.0.0) and
playwright-nightly.yml (v1.2.0) to e2e-version/v3.0.1.

v3 removes the broken react19 preview image from the matrix, so the now
non-existent skip-grafana-react-19-preview-image input is dropped from
playwright-nightly.yml.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@mckn mckn force-pushed the mckn/bump-e2e-version-v3 branch from d2a7bdf to e0f4592 Compare June 22, 2026 10:11
@github-project-automation github-project-automation Bot moved this from 📬 Triage to 🔬 In review in Grafana Catalog Team Jun 22, 2026
@mckn mckn self-assigned this 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 13.0.2
grafana-enterprise 12.1.10
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