Repository navigation
chore: post-v0.25.0 hardening (docs sync + release npm-auth preflight) - #7
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Small follow-ups after the v0.25.0 (0G Router brain) release. No version bump, publishes nothing — merging this only updates
main; prod still moves only on av*tag.What changed
apps/web/app/llms/[[...path]]/route.ts(the llms.txt route, x2) andapps/web/content/docs/11-agents.md(x2) still said0.24.17. Bumped to0.25.0to match the shipped release. (The historical hackathon-window reference in the root README is intentionally left as-is.)bun publishfail with a misleading 404 ("package does not exist in this registry") ~90s into the run, after packing 7 tarballs (this is exactly what bit the v0.25.0 publish). A new early step hits the registry whoami endpoint up front (curl + jq, before setup-bun), so a dead/missing token fails in ~2s with an unambiguous message that points at rotating to a classic Automation token.Verification
bun run lint+bun run typecheck: clean.bash -eo pipefail: empty-token path and invalid-token path both print their guidance and exit 1 (the|| trueon the curl pipeline is what keepsset -e/pipefail from aborting before the message prints).packages/*orcontracts/source touched.https://claude.ai/code/session_01PQ6KBM8gAanXLCFrm4zU7g