docs: (v1) Add root README.md for v1 branch GitHub landing page#1310
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
|
There was a problem hiding this comment.
Important
The v1 test badge image points to tests-badge.yml, which only mirrors test workflow runs for the dev branch, so the badge will not reflect v1 status.
Reviewed changes — replaced the root README.md symlink on the v1 branch with an inlined marketing landing page adapted from main's README.
- Added root
README.md— full landing page with v1 alpha callout, install tabs (npm/pnpm/Yarn/Bun), docs/FAQ/StackBlitz links, and contributor list.
⚠️ v1 test badge will show no status
The badge image at README.md:8 references tests-badge.yml, but that workflow only mirrors test runs when head_branch == 'dev' (.github/workflows/tests-badge.yml:19). On v1 the badge will show no status. Either point the badge image to test.yml for this branch, or extend tests-badge.yml to also mirror v1 runs.
Kimi K2 (free via Pullfrog for OSS) ｜ 𝕏
tests-badge.yml only mirrors dev branch runs, so the badge image showed no status on v1. Use test.yml directly for the badge src instead. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Addressed the Pullfrog review in f0cda69. The test badge image now points at |
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — fixed the v1 test badge source so it reflects actual test.yml runs on the v1 branch.
- Updated
README.mdbadge image — changed the badgesrcfromtests-badge.yml/badge.svg?branch=v1totest.yml/badge.svg?branch=v1, matching the existing link href and ensuring the badge showsv1CI status.
Kimi K2 (free via Pullfrog for OSS) ｜ 𝕏
Split the combined Next.js/Nuxt twoslash test and give each case a 15s timeout. Two sequential TypeScript compilations exceeded Vitest's default 5s limit on the LTS Node matrix job. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Fixed the failing Root cause: Fix: Split the combined test into separate Next.js and Nuxt cases, each with a 15s timeout. |
|
The latest updates on your projects. Learn more about Vercel for GitHub. Warning Deployment cooldown active@autofix-ci[bot] has triggered deployments too frequently. Please wait 18 minutes and 8 seconds before the next automated deployment. ⌛ How to resolve this issue?After the wait time has elapsed, a deployment can be triggered by pushing new commits to this PR or by re-running the workflow. We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?We enforce rate limits to ensure stability and fair usage of resources for all contributors. |
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — since the prior review, the combined Next.js/Nuxt path-alias test was split into two tests with individual 15s timeouts to avoid CI flakiness.
- Split
apps/www/lib/twoslash-options.test.tspath-alias test — separated the Next.js (@/env/client) and Nuxt (~~/env/client) assertions into independent tests so each can carry its own timeout. - Added per-test
timeout: 15_000— gives the Twoslash snippets enough time on CI without raising the global timeout.
Kimi K2 (free via Pullfrog for OSS) ｜ 𝕏
Fixes #1305
Summary
README.mdon thev1branch — previously a symlink topackages/arkenv/README.md, which GitHub renders as the literal stub textpackages/arkenv/README.md— with a full, inlined marketing-style landing page based onmain'spackages/arkenv/README.md.v1-specific adaptations
arkenvinstead of@arkenv/cli(e.g.npx arkenv@latest init)arkenv-v1.vercel.app(all verified to resolve with HTTP 200)branch=v1, StackBlitz usestree/v1/..., and GitHub blob links useblob/v1/...arkenv.js.org) unchangedpackages/arkenv/README.mdis untouched (remains the CLI-focused npm README)Validation
pnpm run typecheck✅pnpm run test✅ (796 tests passed)pnpm run fix✅ (no changes to the new README)Made with Cursor