| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
🦋 Changeset detectedLatest commit: 5875e2c The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Sorry, something went wrong.
|
Codeowners approval required for this PR:
|
Sorry, something went wrong.
|
✅ All changesets look good |
Sorry, something went wrong.
|
The changeset follows the correct format:
The changeset content is accurate to the PR description, the package name is valid, and the version bump type is correct. This is a changeset-only PR with no code changes and no logic to review. LGTM |
Sorry, something went wrong.
Co-authored-by: devin-ai-integration[bot] <158243242+devin-ai-integration[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Codeowners reviews satisfied
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Adds the changeset that #14704 omitted, so that edge-preview-authenticated-proxy actually gets deployed and starts reporting Prometheus metrics again.
What's broken
The Prometheus_Rule_Failed_Checks pint alert has been firing against chat-workers-devprod. pint_problem{owner="chat-workers-devprod"} currently returns 12 series, all for this Worker and none for the other two DevProd Workers:
reporter: promql/series kind: recording filename: /etc/prometheus/recording.d/global_edge_devprod.rules.yaml name: global:devprod_edge_preview_authenticated_proxy_error:ratio15m (and :ratio3h) problem: query on nonexistent series: `edge` Prometheus server at https://edge.prometheus-access.cfdata.org didn't have any series for the `colo:devprod_edge_preview_authenticated_proxy_request:increase15m` metric in the last 1w.The denominator of the SLI doesn't exist because the Worker isn't pushing any counters.
Why
tools/deployments/deploy-non-npm-packages.ts only deploys packages present in PUBLISHED_PACKAGES, i.e. packages that changesets actually version-bumped. All three Workers have wrangler/@cloudflare/workers-utils as devDependencies, so changesets never bumps them automatically. No changeset means no version bump, which means no deploy — the WShim fix was merged over a month ago but has never reached production.
The change
A changeset only, no code changes. changeset status confirms @cloudflare/edge-preview-authenticated-proxy is now queued for a patch bump, which will put it into PUBLISHED_PACKAGES and trigger wrangler deploy on the next release.
Verifying after release
count(edge_preview_authenticated_proxy_devprod_edge_preview_authenticated_proxy_request_total) should become non-empty and pint_problem{owner="chat-workers-devprod"} should go empty. format-errors took ~2 days to reappear after its deploy. The alert has for: 4h, so expect it to resolve a few hours after the series returns.
One thing to watch: #14704 also added secrets.required to this Worker's wrangler.jsonc. Those become inherit bindings and the API hard-fails the deploy if any of PROMETHEUS_TOKEN, SENTRY_ACCESS_CLIENT_SECRET or SENTRY_ACCESS_CLIENT_ID is unset. All three were used by the pre-#14704 code so they should already exist, but that's the first thing to check if the deploy step fails.
A picture of a cute animal (not mandatory, but encouraged)
Note
This is a contribution from an AI agent: OpenCode, claude-opus-5.