fix: update pnpm-lock.yaml for v4.4.5 release

[ericallam]

Summary

The v4.4.5 release PR (#3406) was merged before the automated lockfile-update job in `changesets-pr.yml` could push its commit. As a result main now has `package.json` bumped to `4.4.5` but `pnpm-lock.yaml` still pinned to `4.4.4`.

This blocks every subsequent `pnpm install --frozen-lockfile` run, including:

• `release.yml` for v4.4.5 publish (run #25217579660) — never published packages to npm
• `changesets-pr.yml` on the next push to main (run #25217579645)

Root cause (from CI logs)

```
ERR_PNPM_OUTDATED_LOCKFILE Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with /packages/build/package.json

• @trigger.dev/core (lockfile: workspace:4.4.4, manifest: workspace:4.4.5)
  ```

Regenerated via `pnpm install --lockfile-only` against current main. The diff is exactly what the canceled `update-lockfile` job would have produced:

• 12 `workspace:4.4.4` → `workspace:4.4.5` specifier bumps
• pnpm metadata refresh (deprecation annotations on transitive deps, one optional `bufferutil` peer resolution on `react-email`)

No new direct dependencies, no version drops.

Follow-ups (separate PRs)

1. Re-run release.yml via `workflow_dispatch` (`type: release`, `ref` = merge commit on main once this lands) to actually publish 4.4.5 to npm.
2. Workflow fix to prevent recurrence: fold the lockfile update into `changeset:version` so the `release-pr` job creates a single commit with version bumps + lockfile in sync. Removes the race window where the release PR is mergeable before `update-lockfile` runs.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6bbac57

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

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 41666b81-5d33-4672-806c-bcf0691c13a1

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/release-v4-4-5-lockfile

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}