0 Releases 4,167 Tags

RSS Feed

• v.docker.4.4.5 139cccf27e

  Compare

  fix: update pnpm-lock.yaml for v4.4.5 release (#3498)

  frostbyte_neo released this 2026-05-01 14:37:59 +00:00 | 801 commits to main since this release

  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.

  Downloads

  • Source Code (ZIP)
  • Source Code (TAR.GZ)