Skip to content

Release 0.3.21: threenative login and deploy publish a game from the terminal - #713

Merged
jonit-dev merged 3 commits into
mainfrom
develop
Nov 22, 2026
Merged

jonit-dev merged 3 commits into
mainfrom
develop

Conversation

@jonit-dev

Copy link
Copy Markdown
Contributor

What is this PR about?

It promotes develop to main. The promotion carries the 0.3.21 cohort (create-threenative 0.2.26) and two merged PRs:

Why does it matter?

The release path publishes from a green main. This PR is the one full-board proof for that release. PRD-904's last acceptance check (AC-7) needs this release on npm: a clean room runs npx create-threenative, npx threenative login, npx threenative deploy.

Already live

Local checks run

jonit-dev and others added 3 commits November 22, 2026 00:39
…est work (PRD-903) (#710)

* fix(ci): carry legs again, retry 5xx API reads, skip prose-only develop pushes (PRD-903 phase 1)

- scope's sparse checkout now includes packages/runtime-native/scripts: per-job carry imported
  desktop-build-profile.mjs from there and carried 0 legs on every run. A replay of develop
  41df5bb carries 47 legs. A closure test fails when scope imports a file outside the cone.
- scripts/lib/gh.mjs retries a read twice with a 2 s / 6 s backoff and stops on a 4xx; ghApi in
  scripts/ci/reuse.mjs uses it, so one HTTP 502 no longer drops a whole-tree reuse.
- A develop push whose paths since the last green develop push head are all prose (outside the
  workspace-dist cache-key trees) selects prose; ci-required re-derives that diff.
- native-release.yml cancels a superseded proof on a new pull-request commit (synchronize only).

* perf(release): build the workspace once per ship and poll faster (PRD-903 phase 2)

- npm-release.yml names its built commit in TN_RELEASE_PREBUILT; release.ts skips its own
  pnpm build on an exact HEAD match when provisioning rebuilt no web engine. The proof and the
  publish runs no longer rebuild the same tree (~5 min).
- release-candidate.yml drops its unconditional pnpm build; the gate builds once, on the first
  package npm already serves (~2.5 min on every fresh release).
- release:ship polls every 15 s for ten minutes, then every 60 s.
- PRD: the second upgrade proof, the clean-room serial order, the iOS joins and the
  native-release desktop verify stay, with the reasons under Decisions and Blocked on.

* perf(ci): test stops re-running unit specs; budget probe runs once (PRD-903 phase 3)

- In prebuilt mode (CI `test`), terrain, procedural-environment, procedural-animals,
  blender-bridge and strata-terrain-preview leave the recursive package walk. The walk keeps
  publint for all eight packages, the strata bake and test:water, and drops their root-config
  vitest re-runs (the test-unit shards own those files) and package rebuilds. Local paired run:
  47 s against more than 280 s; CI baseline 9.7 min.
- template-assets-compile probes the uncooked budget on starter only; every kit still compiles.
  Local paired run: 155 s -> 125 s.
- PRD: the terrain-mcp and city ceilings are coverage cuts and move to Blocked on (owner).

* docs(prd): PRD-903 waits only on the next release's timings; Android sharding moves to PRD-904

Owner chose the review lane only for PRD-903's live CI. Android 2-way sharding and the
integration-lane grouping need a one-APK producer and native CI runs, so they move to the new
PRD-904 as a follow-up. PRD-903's last open item is AC-4 (live timings on the next release),
so it moves to BLOCKED/requires-next-release/ (R6).

* test(ci): run-test-suite guard derives no package names (TN_WORKSPACE_PACKAGE_LITERAL_ENUMERATION)

The budgets gate rejects a literal workspace package list in a spec. The walk-body guard
(publint kept, no vitest) still covers the behaviour; the name list was redundant.
… Publish button (PRD-904) (#712)

* docs(prd): PRD-904 tn login and tn deploy delegate to the store CLI's device flow and push

* docs(create-threenative): drop the two-commands-ever rule; new commands borrow established CLI names (owner, 2026-11-21)

* docs(prd): PRD-904 deploy matches Studio's Publish share link; login is the site device flow in TypeScript

* docs(prd): PRD-904 folds in the Gemini review: logout revokes, terms rule on CLI tokens, .threenative/ link, device page keeps the code

* docs(prd): PRD-904 records the tokenAccount and terms-on-approve decisions

* feat(create-threenative): threenative login, logout and deploy publish to the Studio share link (PRD-904)

login runs the threenative.com device flow and saves a 0600 token (THREENATIVE_TOKEN overrides);
logout revokes it on the site; deploy runs build:web, packs dist/ in Studio's share archive format,
PUTs it to Studio's /api/cli/share and keeps the link in .threenative/share.json.

* docs(prd): PRD-904 AC-1, AC-5 and AC-6 pass on the local site and Studio Workers

* fix(create-threenative): logout keeps a token it could not revoke; atomic 0600 token write; a dropped body exits 5 (PRD-904 Sol review)

* fix(create-threenative): unique temp token file, accurate logout help, first deploy carries a key so a lost reply retries onto one game (PRD-904 Sol re-review)

* docs(prd): PRD-904 AC-6 reruns green after the Sol review fixes

* fix(create-threenative): share.json is written through a temp file and renamed, so an interrupted write cannot lose the deploy key (PRD-904 Sol review 3)

* fix(create-threenative): two first deploys from one checkout claim one deploy key through an atomic link (PRD-904 Sol review 4)

* fix(create-threenative): logout deletes the token file only while it still holds the revoked token (PRD-904 Sol review 8)

* fix(create-threenative): logout claims the token file with one rename and login writes it once, so neither loses or revives the other's token (PRD-904 Sol review 9)

* fix(create-threenative): logout keeps an unrevoked or interrupted token in its claimed file and retries it next time; an empty whoami reply still saves the token (PRD-904 Sol review 10)

* fix(create-threenative): logout revokes on the issuing site and keeps a file it cannot read; empty replies exit 4; the deploy key claim works without hard links (PRD-904 Sol review 11)

* fix(create-threenative): a half-made share.json is waited for or removed, and logout claims auth.json in a directory it cannot list (PRD-904 Sol review 12)

* fix(create-threenative): logout exits 4 when it cannot list the config directory and has nothing to claim, instead of saying signed out (PRD-904 Sol review 13)

* docs(prd): PRD-904 records the Sol 6.2 approval and the final local end-to-end

* docs(create-threenative): the CLI surface paragraph fits the 100-line instruction cap (PRD-904 merge-queue red)
Prepared with `pnpm release:prepare` and `pnpm scaffold:pin`: core and the cohort 0.3.20 -> 0.3.21,
create-threenative 0.2.25 -> 0.2.26. Carries #710 and #712 (PRD-904: threenative login, logout and deploy).

proof: prepare-release (17 packages, 6 MCP servers, nothing published), scaffold pins 16 kits
@github-actions

Copy link
Copy Markdown
Contributor

This promotion board ended with 1 red leg.
The board ran to its end, so this list is every leg of the round that did not pass.

Board: 44994406950

Fix them together, push once, and the next board carries the next fix set.

@jonit-dev
jonit-dev merged commit 747f767 into main Nov 22, 2026
214 of 218 checks passed
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.

1 participant