Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

capnweb-validate@0.2.2

Patch Changes

• #197 0409821 Thanks @teamchong! - Treat Workers fetch and connect lifecycle methods as passthrough methods on WorkerEntrypoint and DurableObject targets.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/cloudflare/capnweb@199

commit: c387b85

[teamchong]

Why this PR keeps getting stuck (and the empty commit I just pushed)

The main ruleset requires the CLAssistant status check on the PR head commit. This release PR is opened/updated by github-actions[bot] using the built-in GITHUB_TOKEN, and GitHub deliberately does not trigger pull_request_target from GITHUB_TOKEN-initiated events (anti-recursion). So cla.yml never runs against this PR's head, the required CLAssistant check never attaches, and the PR sits BLOCKED on "Expected — waiting for status to be reported".

What does / doesn't move it (verified against the run head_shas):

• recheck / comments → fire issue_comment, which runs against the default branch, so the CLAssistant check lands on main, not this PR head. Goes green but never satisfies the requirement.
• Close/reopen → reopened isn't in the trigger list and reopening doesn't emit opened, so nothing runs.
• An empty commit → fires pull_request_target: synchronize, which attaches CLAssistant to the new head. This is the only human-firable trigger that currently works, which is why I pushed an empty commit here to unblock this release.

Proposed follow-up fix (no PAT / no admin needed)

Add labeled to the pull_request_target triggers in .github/workflows/cla.yml:

on:
  issue_comment:
    types: [created]
  pull_request_target:
    types: [opened, synchronize, labeled]
  merge_group:

A maintainer adding a label is a human-initiated pull_request_target event (not suppressed by GITHUB_TOKEN), and pull_request_target always attaches its check to the PR head — so labeling the PR lands CLAssistant on the head without an empty commit. After that, just approve + squash-merge.

(The durable, fully-automatic fix would be to have the Changesets action open the release PR with a PAT/GitHub App token instead of GITHUB_TOKEN, so pull_request_target fires on its own — but that needs a secret, i.e. admin. The labeled trigger is the cheap, no-admin substitute.)

Leaving this as a follow-up; the empty commit above is just to get this release out for now.