Bump the html-eslint group across 1 directory with 2 updates

[dependabot]

Bumps the html-eslint group with 2 updates in the /frontend directory: @html-eslint/eslint-plugin and @html-eslint/parser.

Updates @html-eslint/eslint-plugin from 0.61.0 to 0.62.0

Release notes

Sourced from @​html-eslint/eslint-plugin's releases.

v0.62.0

What's Changed

• chore(deps): bump @​mdn/browser-compat-data from ^7.3.16 to 8.0.2 by @​github-actions[bot] in yeonjuan/html-eslint#611
• chore(deps): bump tmp from 0.2.3 to 0.2.6 by @​dependabot[bot] in yeonjuan/html-eslint#612
• fix: ignore template expression check in indent by @​yeonjuan in yeonjuan/html-eslint#615

Full Changelog: yeonjuan/html-eslint@v0.61.0...v0.62.0

Commits

• eb5fa83 v0.62.0
• 2e6f6dc fix: ignore template expression check in indent (#615)
• eb22081 chore(deps): bump tmp from 0.2.3 to 0.2.6 (#612)
• eea5aab chore: bump @​mdn/browser-compat-data from ^7.3.16 to 8.0.2 (#611)
• See full diff in compare view

Updates @html-eslint/parser from 0.61.0 to 0.62.0

Release notes

Sourced from @​html-eslint/parser's releases.

v0.62.0

What's Changed

• chore(deps): bump @​mdn/browser-compat-data from ^7.3.16 to 8.0.2 by @​github-actions[bot] in yeonjuan/html-eslint#611
• chore(deps): bump tmp from 0.2.3 to 0.2.6 by @​dependabot[bot] in yeonjuan/html-eslint#612
• fix: ignore template expression check in indent by @​yeonjuan in yeonjuan/html-eslint#615

Full Changelog: yeonjuan/html-eslint@v0.61.0...v0.62.0

Commits

• eb5fa83 v0.62.0
• 2e6f6dc fix: ignore template expression check in indent (#615)
• eb22081 chore(deps): bump tmp from 0.2.3 to 0.2.6 (#612)
• eea5aab chore: bump @​mdn/browser-compat-data from ^7.3.16 to 8.0.2 (#611)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[github-actions]

Warning

Flaky specs

• rspec ./modules/wikis/spec/features/admin/internal_provider_spec.rb[1:1]

🤖 Ask Copilot to investigate

Copy the prompt below into a new comment on this PR to delegate the investigation to GitHub Copilot. It will look into the flakiness and open a separate pull request with you as reviewer.

@copilot The following spec(s) are flaky in CI (first seen on PR #23901, linked for reference only):

- `rspec ./modules/wikis/spec/features/admin/internal_provider_spec.rb[1:1]`

Treat this as a standalone task, unrelated to PR #23901. Create a new branch from origin/dev and open a new pull request targeting dev — do not stack it on PR #23901 or reuse that branch.

Follow the playbook in docs/development/testing/handling-flaky-tests/README.md to find the root cause and fix the underlying race — do not skip, delete, or weaken the spec to make it pass; disabling is a last resort per the playbook, and only with a bug ticket. Verify the fix by running the spec(s) repeatedly (e.g. `script/bulk_run_rspec --run-count 10`).

If you cannot reproduce the flake or are not confident in a fix after reasonable investigation, do not fabricate a change or skip the spec to force CI green. Instead, leave the pull request in draft and document what you tried, the suspected cause, and any leads in its description, then assign @dependabot[bot] to take over.

Once the fix is verified, title the PR after the spec(s) it fixes, and use the PR description to explain the root cause, how the change resolves it, and the before/after results. Label the PR `flaky-spec`, assign @dependabot[bot], and request a review from @dependabot[bot].
On every commit, set @dependabot[bot] as the sole co-author with a `Co-authored-by:` trailer (use their GitHub no-reply email so it links to their account), so it is traceable who dispatched the fix.