Update Yarn to v4.14.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
yarn (source)	4.13.0 → 4.14.1

---

Release Notes

yarnpkg/berry (yarn)

v4.14.1

Compare Source

v4.14.0

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "every weekend,every weekday after 5pm,every weekday before 8am"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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.

[teemow]

@renovatebot rebase

[teemow]

Smoke-test status (marge sweep 2026-04-27)

After Renovate rebase the smoke-test re-ran and reached the deployment stage, then failed at:

test_backstage_deployment_ready - TimeoutError: Error waiting for object of type <class 'pykube.objects.Deployment'>

So Yarn 4.14.1 builds successfully (the chart packages and image pushes), but the resulting Backstage deployment never reaches Ready in the smoke-test KinD cluster within the timeout. This is no longer a Yarn 3->4 build issue, it's a runtime issue in the produced container.

Likely causes worth investigating before this can merge:

• Yarn 4 PnP / module resolution differences breaking container startup at runtime (check pod logs from the smoke-test, not just the chart deploy)
• backstage-cli 0.34 + Yarn 4 require an explicit nodeLinker: node-modules or migration step the upstream Backstage 1.50 release notes call out
• Worker / dynamic-plugins-root paths now resolved differently

This needs a dedicated Backstage migration session, not a dependency-bump sweep. Leaving the PR open.

[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.

[teemow]

This PR is blocked by an unrelated better-sqlite3 native binding failure in plugins/ai-chat-backend/src/services/ConversationStore.test.ts -- the same issue reported in WiseLibs/better-sqlite3#1384 (missing prebuild-install binaries for Node 24 / N-API 137).

The Yarn 4.14.1 upgrade itself is correct (binary swap + lockfile metadata bump). The buildjob has been re-triggered twice with the same result, while a sibling renovate PR with no Yarn change (#1599) passes the same buildjob. The failure is reproducible on Yarn 4.14.1 but not on 4.13.0 because the new prebuild-install flow appears to skip the legacy postinstall path that 4.13.0 still hits via the bundled yarn binary.

Options:

1. Wait for better-sqlite3 to ship Node 24 prebuilds, then rebase.
2. Add enableScripts: true (or equivalent) to .yarnrc.yml and pin better-sqlite3 so postinstall builds from source. Needs verification that the CircleCI image has the toolchain.
3. Stick with Yarn 4.13.0 until the upstream issue resolves.

Marked for re-triage rather than auto-merging via marge sweep.

[marians]

See teemow's comment