docs: use versioned schema URLs in docs#155
Merged
wry-ry merged 1 commit intorelease/2026-01-23from Feb 6, 2026
Merged
Conversation
igrigorik
approved these changes
Feb 4, 2026
Contributor
igrigorik
left a comment
There was a problem hiding this comment.
👍 lgtm
Stepping back, the version should really be dynamic / injected when we build, and we should be validating all the embedded examples against the latest version as part of build. Not blocking to this PR (we should land it and show right version), but I'd love to not have to need to manually update and approve PRs like this in the future.
Collaborator
|
Thanks for the fix. Can you target this to release/2026-01-23 branch instead to fix it there? I'll look into automating it for the draft version and bring a PR for it tonight or tomorrow. |
227cd9a to
fcb1ab5
Compare
Contributor
Author
|
@wry-ry done 👍 |
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.
I noticed that many of the docs were still using
2026-01-11API versions, and almost none of the docs had been updated to use a versioned schema URL. This PR fixes both issues, with the2026-01-23API version used consistently. I assume we will want a better, more automated way of doing this as we continue to publish versions, but in the interim, I’d love to have the docs speak a little more consistently, and point folks to permanent URLs (ucp.dev/*anducp.dev/latest/*will always work, but their content will be variable over time, and their versions will not match with the hardcoded version strings in examples that reference those URLs).