Skip to content

fix: correct deploy token command hint to npx void auth token - #89

Merged
Brooooooklyn merged 1 commit into
mainfrom
fix-void-token-hint
Apr 8, 2026
Merged

Brooooooklyn merged 1 commit into
mainfrom
fix-void-token-hint

Conversation

@Boshen

@Boshen Boshen commented Apr 8, 2026

Copy link
Copy Markdown
Member

Summary

  • Fix GitHub Actions setup hint in void init to point to the correct command npx void auth token instead of the non-existent void token.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@Brooooooklyn
Brooooooklyn merged commit e4e8365 into main Apr 8, 2026
7 checks passed
@Brooooooklyn
Brooooooklyn deleted the fix-void-token-hint branch April 8, 2026 07:51
cpojer pushed a commit that referenced this pull request Sep 11, 2026
…ssions (#89)

* test(api): add e2e coverage for D1 migration edge cases and fix regressions

Adds an e2e integration test suite for /migrations/apply, /migrations/rename,
and /rollback that exercises concurrent callers, destructive SQL guards,
quoted/bracketed identifiers, block-comment obfuscation, legacy-table
upgrade races, migration-rename persistence, and rollback diff
enforcement.

Fixes the regressions the suite surfaced:
- Serialize /apply, /rename, and /rollback per project via row lock
  (SELECT id FROM projects WHERE id = $1 FOR UPDATE) instead of a
  32-bit hashtext advisory key.
- Remote D1 runner now wraps response.json() in an AbortController so
  a slow body read cannot outlive the migration timeout.
- New migration_renames table persists rename history; /rename
  corroborates applied state across deployments via it.
- Destructive-SQL guards broadened: block comments, quoted
  semicolons, pragma-must-be-standalone, ALTER RENAME narrowed to
  RENAME TO / RENAME COLUMN.
- Destructive rollback now requires the caller to echo the
  currentActive→target migration diff; server rejects if its
  in-lock view of the set has drifted.

Bumps framework to include the runner IMMEDIATE-transaction hardening
and the matching CLI-side allowDestructive rollback option.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* test(api): drain deploy NDJSON stream in status-only deploy tests

The /deploy route runs its work (including deployments-table writes via
createDeployment and updateDeploymentStatus) inside a fire-and-forget
IIFE that streams NDJSON back to the client. Tests that asserted the
200 status without reading the body let the IIFE run past the test's
return, racing the next beforeEach's clearTables — delete(deployments)
ran against zero rows, the IIFE then inserted, and delete(projects)
failed the FK.

Adds `await readAllEvents(res)` after the status assertion in the two
remaining offenders. `succeeds with static SPA deploy (passthrough
worker)` was the downstream victim whose beforeEach lost the FK race;
its own body is already drained.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
cpojer pushed a commit that referenced this pull request Sep 11, 2026
* feat(api): per-project cpuMs override with plan ceiling (bump framework)

Honors the new manifest field limits.cpuMs (void.json worker.limits.cpu_ms,
#299) when building routing dispatch limits:

- tiers.ts: PlanLimits.maxCpuMsPerRequest, the highest cpuMs a project
  may request (free 10, solo/pro/sponsored 30_000, custom 0 = no ceiling)
- deploy ingest: validate manifest.limits shape; reject an over-ceiling
  cpuMs with 400 naming both numbers, before the claim transaction
- routing.ts: shared computeDispatchLimits replaces the duplicated
  inline expressions at deploy go-live and rollback; byte-identical
  output for manifests without limits
- rollback clamps to the current plan ceiling instead of rejecting, and
  an out-of-domain stored cpuMs (0, negative, fractional - storable
  through the pre-validation API skew window) falls back to the plan
  default instead of erasing the cap
- dispatch unchanged: routing.limits was already applied verbatim

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DF8p6MCmgiE7e3LM1J8EQV

* fix(api): replace zero-width spaces in comments with backslash escapes

`vp lint` has failed on main since the vite+ 0.3.0 bump (#262): the newer
oxlint enforces no-irregular-whitespace, which flags six U+200B zero-width
spaces added in #89. Every one sits inside a quoted `*/`, where it stops
the sequence from closing the enclosing comment.

Deleting them is not safe. Four are inside `/** */` docstrings, where a
bare `*/` truncates the comment and breaks the file. Those use `*\/`,
which the tokenizer does not treat as a terminator. The remaining two are
inside `//` line comments, where `*/` needs no escape at all.

Unblocks CI for this PR and every branch cut after #262.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Grrh3fMQxnc3MKfJWKg7Vv

* chore(api): track the framework submodule at void CLI 0.10.12

The rebased submodule pointer moves the framework from 0.10.10 to
0.10.12, and both fallback CLI constants must follow it. They only
apply to repos with no local `void` dependency, so drift never shows
up in an ordinary build — `build-manager.test.ts` is what catches it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Grrh3fMQxnc3MKfJWKg7Vv

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants