Bump workerd from 1.20260625.1 to 1.20260626.1 in the workerd-and-workers-types group#14432
Conversation
Bumps the workerd-and-workers-types group with 1 update: [workerd](https://github.com/cloudflare/workerd). Updates `workerd` from 1.20260625.1 to 1.20260626.1 - [Release notes](https://github.com/cloudflare/workerd/releases) - [Changelog](https://github.com/cloudflare/workerd/blob/main/RELEASE.md) - [Commits](cloudflare/workerd@v1.20260625.1...v1.20260626.1) --- updated-dependencies: - dependency-name: workerd dependency-version: 1.20260626.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: workerd-and-workers-types ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
ci:skip-pr-description-validation
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
dependabot
Bot
added
dependencies
|
workers-devprod
requested review from
a team and
ascorbic
and removed request for
a team
|
Codeowners approval required for this PR:
Show detailed file reviewers
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| playwright-chromium: "1.60.0" | ||
| "@cloudflare/workers-types": "^4.20260625.1" | ||
| workerd: "1.20260625.1" | ||
| workerd: "1.20260626.1" |
There was a problem hiding this comment.
🔴 Lockfile not updated after dependency version bump, causing install failures
The lockfile still resolves the old version (specifier: 1.20260625.1 in pnpm-lock.yaml) after the declared version was bumped (pnpm-workspace.yaml:123), so pnpm install --frozen-lockfile in CI will fail due to the specifier mismatch.
Impact: CI builds will fail, or users will silently get the wrong runtime version installed.
Lockfile specifiers are stale after catalog version change
The catalog in pnpm-workspace.yaml:123 was updated from workerd: "1.20260625.1" to workerd: "1.20260626.1", and packages/miniflare/package.json:55 and packages/wrangler/package.json:87 were also updated. However, the pnpm-lock.yaml still contains specifier: 1.20260625.1 for both miniflare and wrangler's workerd dependency, and there are zero references to 20260626 anywhere in the lockfile. The lockfile diff only contains unrelated changes (vitest resolution shuffles, bson version bump).
Per AGENTS.md: "After updating dependencies, always run pnpm i to also update the package lock file." This was not done for the workerd bump, so the lockfile is out of sync with the workspace configuration.
Prompt for agents
The pnpm-lock.yaml was not updated to reflect the workerd version bump from 1.20260625.1 to 1.20260626.1. The lockfile still references the old version (specifier: 1.20260625.1) in two places (miniflare and wrangler importers). Run `pnpm install` (or `pnpm i`) in the repository root to regenerate the lockfile with the correct workerd version, then commit the updated pnpm-lock.yaml.
Was this helpful? React with 👍 or 👎 to provide feedback.
1 participant
Bumps the workerd-and-workers-types group with 1 update: workerd.
Updates
workerdfrom 1.20260625.1 to 1.20260626.1Release notes
Sourced from workerd's releases.
Commits
447e337Release 2026-06-26Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions