chore(deploy): empty commit to force CF Workers Builds rebuild#144
Merged
Conversation
Workers Builds reported success on 1a1fd4e (PR #141 merge) at 2026-04-26T19:18:49Z, but the deployed bundle is still serving pre-#141 tracing.ts (envelope still has `index_source` field that was deleted in the refactor; no `fetches[]` array). Suspect stale build cache or ref-tracking issue on the CF integration. This empty commit gives the build a fresh SHA to react to. If this doesn't resolve within ~5 min, the next step is dashboard-side investigation of Workers Builds settings — not a code fix.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
oddkit | d627eb7 | Commit Preview URL Branch Preview URL |
Apr 26 2026, 08:56 PM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Empty commit to force CF Workers Builds to rebuild and redeploy.
Why
Workers Builds reported
successon1a1fd4e(PR #141 merge) at 2026-04-26T19:18:49Z, but the deployed bundle is still serving pre-#141 code:index_sourcefield (deleted in refactor(telemetry): retire indexSource interpreter — fetchers report, telemetry tallies #141)fetches[]array, nocacheStatsobject (added in refactor(telemetry): retire indexSource interpreter — fetchers report, telemetry tallies #141)serverInfo.versionreports0.25.0(env var bumped) but the bundle itself is staleSUM(cache_hits) / SUM(cache_lookups)telemetry query fails — deployed SchemaMap doesn't recognize the new doublesSuspect a stale build cache or ref-tracking issue on the CF Workers Builds integration. Empty commit gives it a fresh SHA to react to.
If this doesn't work
Next step is dashboard-side — re-trigger Workers Builds manually from the CF UI, or check the build settings for path filters / cache config that may be skipping the rebuild.
Note
Low Risk
No functional code changes; this is an empty commit intended to force a redeploy, so risk is limited to CI/CD behavior and deployment timing.
Overview
This PR makes no code changes and exists solely to create a new commit SHA to trigger Cloudflare Workers Builds to rebuild and redeploy the worker bundle.
Reviewed by Cursor Bugbot for commit d627eb7. Bugbot is set up for automated code reviews on this repo. Configure here.