Files
wehub-resource-sync 70bf21e064
Deploy (to testing) and Test Playground Preview Worker / Deploy Playground Preview Worker (testing) (push) Has been skipped
Deploy Workers Shared Staging / Deploy Workers Shared Staging (push) Failing after 0s
Prerelease / build (push) Has been skipped
Handle Changesets / Handle Changesets (push) Has been cancelled
Semgrep OSS scan / semgrep-oss (push) Has been cancelled
chore: import upstream snapshot with attribution
2026-07-13 12:30:11 +08:00

7.0 KiB

devprod-status-bot

1.5.0

Minor Changes

  • #13911 2115e8a Thanks @WillTaylorDev! - Post a Chat alert when an issue is opened with the api label, or when the api label is added to an existing issue

    Routes alerts to a new API_ISSUES_WEBHOOK so the team room watching the Workers SDK community channel gets realtime visibility into incoming api-tagged issues.

1.4.2

Patch Changes

  • #13850 1527003 Thanks @penalosa! - Migrate bot message generation off the deprecated @cf/meta/llama-2-7b-chat-int8 Workers AI model

    Workers AI is deprecating Llama 2 7B chat (alongside several other older models) on May 30th 2026. The status bot now uses @cf/google/gemma-4-26b-a4b-it (Gemma 4) for generating its short, friendly chat messages.

1.4.1

Patch Changes

  • #12435 c2163df Thanks @petebacondarwin! - Simplify Version Packages PR CI failure alerts

    The bot now sends an alert for any failing CI job on the Version Packages PR, instead of first fetching the required status checks from GitHub's branch protection API and filtering. This removes unnecessary complexity and ensures all CI failures are reported.

1.4.0

Minor Changes

  • #12371 50ad9a9 Thanks @petebacondarwin! - Send alert to ANT: Alerts chat on failed CI checks in Version Packages PRs

    When a required CI check fails or times out on the Version Packages PR (changeset-release/main branch), an alert is now sent to the ANT: Alerts Google Chat channel. This helps the team quickly identify and address CI failures that shouldn't occur since individual PRs have already passed before landing on main.

    Alerts for the same PR are grouped into the same chat thread using the PR number as the thread ID.

1.3.0

Minor Changes

1.2.3

Patch Changes

1.2.2

Patch Changes

1.2.1

Patch Changes

1.2.0

Minor Changes

1.1.7

Patch Changes

1.1.6

Patch Changes

1.1.5

Patch Changes

1.1.4

Patch Changes

1.1.3

Patch Changes

1.1.2

Patch Changes

1.1.1

Patch Changes

1.1.0

Minor Changes

1.0.0

Major Changes