Update dependency qunit-dom to v3.6.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
qunit-dom	3.5.1 → 3.6.0

---

Release Notes

mainmatter/qunit-dom (qunit-dom)

v3.6.0

• qunit-dom 3.6.0 (minor)

🚀 Enhancement

• qunit-dom
  • #​2215 Add is() and isNot() element identity assertions (@​NullVoxPopuli-ai-agent)

🏠 Internal

• qunit-dom
  • #​2216 chore: support release-plan OIDC (@​BobrImperator)

Committers: 2

• @​NullVoxPopuli's reduced-access machine account for AI usage (@​NullVoxPopuli-ai-agent)
• Bartlomiej Dudzik (@​BobrImperator)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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]

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

---

• Branch has one or more failed status checks

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

Error: ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION

  × installing dependencies
  ╰─▶ 1 lockfile entries failed verification:
        @embroider/macros@1.21.3 was published at 2026-10-05T22:43:40.000Z,
      within the minimumReleaseAge cutoff (2026-10-05T06:12:33.352Z)
  help: The lockfile contains entries that the active policies reject. This
        can mean the lockfile is stale, or that someone committed a lockfile
        that bypassed the policy locally — inspect recent changes to pnpm-
        lock.yaml before trusting it. If the changes look expected, run "pnpm
        clean --lockfile" and then "pnpm install" to rebuild from a fresh
        resolution. If the fresh resolution still fails and you trust the
        affected packages, relax the policy that flagged them.