chore(deps): bump open from 11.0.2 to 11.0.3

[dependabot]

Bumps open from 11.0.2 to 11.0.3.

Release notes

Sourced from open's releases.

v11.0.3

• Fix Windows launches being killed when the parent process exits 734b821

---

sindresorhus/open@v11.0.2...v11.0.3

Commits

• 81deafb 11.0.3
• 734b821 Fix Windows launches being killed when the parent process exits
• See full diff in compare view

[changeset-bot]

⚠️ No Changeset found

Latest commit: 527df6b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

🤖 Bip Bop - Automated Dependency review of open@11.0.3

Note

Model: gpt-5.6-luna
Reviewed commit: 527df6b8ac90
Workflow: View research run

🟢 Verdict: MERGE

Confidence: high

Readiness: waiting for checks

The patch is a semver-patch update with a narrowly targeted Windows process-lifecycle fix. It preserves the package API and Node engine requirement; repository usage is compatible, with no evidence of security or runtime incompatibility. Technical verdict is independent of the currently pending checks and required approval.

Key findings

• Dependency: open 11.0.2 → 11.0.3; only pnpm-lock.yaml changed (PR diff).
• Upstream behavior: 11.0.3 makes Windows and Windows-in-WSL launcher processes wait for close, preventing PowerShell from being killed when the parent exits; non-fallback launches still do not reject on non-zero exit (upstream release, upstream diff).
• Call-site compatibility: AuthProviderInteractive imports open and awaits openBrowser(authCodeUrl) without an explicit opt-out. The new default Windows behavior therefore applies to the repository’s browser-login path (call site).
• Security: No upstream advisory or attack-surface change was identified; the release is a Windows reliability fix.
• Discussion: No review threads or reviewer objections are present. The changeset bot reports no changeset; this is compliant because the PR is lockfile-only and changes no package manifest (repository policy).
• Checks: Code quality has completed successfully. Build affected packages, Unit tests, both Playwright jobs, and the dependency research check remain in progress. Completed static validation does not cover Windows browser-launch integration; the upstream release includes a Windows regression test, but repository-level runtime coverage remains pending.

Repository impact

• Affects published-package dependency resolution for @equinor/fusion-framework-cli and @equinor/fusion-framework-module-msal-node; their declared range already admits 11.0.3.
• The branch is mergeable and is 0 commits behind current main (behind_by: 0) (compare API).
• Merge is mechanically blocked by the active repository ruleset’s one required approval and required review-thread resolution; no unresolved threads currently exist (ruleset).

Merge path

• Wait for the pending repository checks, especially Windows Playwright validation.
• Obtain the required approving review.
• Maintainer decides whether to merge; dependency workflow can rebase the branch and add any required dependency changesets if repository state changes, but merge remains a maintainer decision.

Generated by Fusion AI using the repository dependency-review skill.

[dependabot]

Superseded by #5576.