Update docker/login-action action to v3.5.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
docker/login-action	action	minor	v3.4.0 -> v3.5.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

docker/login-action (docker/login-action)

v3.5.0

Compare Source

• Support dual-stack endpoints for AWS ECR by @​Spacefish @​crazy-max in https://github.com/docker/login-action/pull/874 https://github.com/docker/login-action/pull/876
• Bump @​aws-sdk/client-ecr to 3.859.0 in https://github.com/docker/login-action/pull/860 https://github.com/docker/login-action/pull/878
• Bump @​aws-sdk/client-ecr-public to 3.859.0 in https://github.com/docker/login-action/pull/860 https://github.com/docker/login-action/pull/878
• Bump @​docker/actions-toolkit from 0.57.0 to 0.62.1 in https://github.com/docker/login-action/pull/870
• Bump form-data from 2.5.1 to 2.5.5 in https://github.com/docker/login-action/pull/875

Full Changelog: docker/login-action@v3.4.0...v3.5.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[github-actions]

Playwright test results

Image Name	Version	Result	Report
grafana-dev	12.2.0-258070	❌	View report

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.