Skip to content

docs(roadmap): mark v0 alpha banner and CLI import guard as done #1741

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
yamcodes merged 3 commits into from
Sep 2, 2026
Merged

docs(roadmap): mark v0 alpha banner and CLI import guard as done #1741

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
06ffdb9
docs(roadmap): mark v0 alpha banner and CLI postinstall guard as done
yamcodes Sep 2, 2026
97a576c
docs(roadmap): retitle CLI guard item to import guard
yamcodes Sep 2, 2026
c70fc40
docs(runbook): clarify import guard error phrasing in step 2.4
yamcodes Sep 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions apps/www/lib/roadmap/config.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ export const ROADMAP_EXTRAS: readonly RoadmapExtra[] = [
{
id: "v0-alpha-banner",
title: "v0 site Alpha banner",
done: false,
done: true,
topic: "Docs",
},
{
Expand All @@ -61,8 +61,8 @@ export const ROADMAP_EXTRAS: readonly RoadmapExtra[] = [
},
{
id: "cli-postinstall-guard",
title: "Add CLI postinstall guard for v0 upgrades",
done: false,
title: "Add CLI import guard for v0 upgrades",
done: true,
Comment thread
yamcodes marked this conversation as resolved.
topic: "CLI",
},
{
Expand Down
6 changes: 3 additions & 3 deletions docs/LAUNCH_RUNBOOK.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ This runbook outlines the operational, DNS, npm registry, and deployment steps r
- Deploy a frozen snapshot of the `dev` (v0) documentation branch to Vercel/Cloudflare Pages.
- Assign domain: `v0.arkenv.js.org`.
- Verify that old links, guides, and v0 API references resolve correctly.
- [ ] **Alpha Banner on Live v0 Site (`dev` branch)**:
- [x] **Alpha Banner on Live v0 Site (`dev` branch)**:
- Add announcement banner to `arkenv.js.org` (pointing to `https://arkenv-v1.vercel.app` and migration guide) during the final testing window.
- [ ] **README and Production Links**:
- Update all alpha links (`arkenv-v1.vercel.app`) in READMEs and docs to `arkenv.js.org`.
Expand Down Expand Up @@ -56,9 +56,9 @@ Execute npm deprecation for the old v0 CLI package name:
npm deprecate @arkenv/cli "This package was renamed to 'arkenv' in v1. Please update your dependencies: 'npm i -D arkenv' and use '@arkenv/core' for runtime validation."
```

### Step 2.4: Validate CLI Postinstall & Import Guards
### Step 2.4: Validate CLI Import Guard

- Verify that `npm install arkenv` / `import arkenv from "arkenv"` throws the clear runtime error guiding users to `@arkenv/core`.
- Verify that importing or requiring `arkenv` as a library (`import arkenv from "arkenv"` / `require("arkenv")`) throws the clear runtime error guiding users to `@arkenv/core`.
- Test running `npx arkenv init` in a fresh project to ensure it executes without errors.

---
Expand Down
Loading