Restore cf:service=supermemory tag on supermemory worker#1147
Draft
Dhravya wants to merge 1 commit into
Draft
Conversation
The supermemory-app Cloudflare Worker lost its cf:service=supermemory tag after a batch redeployment. Add the tags field to wrangler.jsonc so the tag is applied on every subsequent deploy, preventing it from being silently dropped again. No worker code, bindings, or other configuration is changed. Co-authored-by: Dhravya Shah <dhravya@supermemory.com>
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
supermemory-mcp | 9ab2860 | Jun 21 2026, 07:46 AM |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
supermemory-app | 9ab2860 | Commit Preview URL Branch Preview URL |
Jun 21 2026, 07:47 AM |
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
2 participants
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.
Summary
The Cloudflare Worker for the supermemory web application lost its
cf:service=supermemorytag after a batch redeployment. This PR restores it by adding thetagsfield toapps/web/wrangler.jsoncso the tag is applied on every subsequent deploy.Changes
apps/web/wrangler.jsonc: Added"tags": ["cf:service=supermemory"]to the top-level worker configuration.Assumptions & Investigation Notes
The Polylane autofix report referenced a Cloudflare Worker named
supermemory(account47c2b4d598af9d423c06fc9f936226d5) that lost itscf:service=supermemorytag. After searching the repository:"name": "supermemory"exists in this monorepo.supermemory-mcp(apps/mcp/wrangler.jsonc) andsupermemory-app(apps/web/wrangler.jsonc).api.supermemory.ai) that is not tracked in this repo — that worker may be the one originally namedsupermemory.supermemory-consumerthen renamed tosupermemory-app; neither matchessupermemoryexactly.Given the ambiguity, the tag is applied to
supermemory-app(the primary consumer-facing web application) as the best available candidate. If the tag should instead go on a different worker (e.g., a private API repo), this PR demonstrates the pattern to follow there.Scope
No worker code, bindings, routes, or observability configuration is changed. This is a pure metadata addition.