Change metadata base#231
Merged
Merged
Conversation
jonnyparris
approved these changes
Jun 11, 2026
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.
Type of Change
wrangler.toml— setsMETADATA_BASEfor staging and production.What issue does this relate to?
Follow-up to #230. That PR changed the dev-default metadata URL; this PR sets the explicit per-env values for the deployed workers.
What should this PR do?
https://metadata-staging.cdnjs.cloudflare.comhttps://metadata.cdnjs.cloudflare.comWhat are the acceptance criteria?
api.cdnjs.devlibrary lookups work after staging deployapi.cdnjs.comlibrary lookups work after production deploy