Repository navigation
chore(release): cut 0.0.9 - #2598
Merged
Merged
Conversation
Assert exact public release pins before localizing auth and Postgres fixtures. Prepare the locked Postgres graph for its actual Prisma config probe entrypoint. Retain every real subprocess and behavior assertion. Refs #2474
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.
Summary
Cut NetScript 0.0.9.
Validation
deno task release:preflightdeno task publish:dry-rundeno ci --prodPost-Merge
Create and publish GitHub Release
v0.0.9;publish.ymlwill publish with OIDC and hand the published version toe2e-cli-prod.yml.Canary pair (stable gate)
This bump is version-only, plus generator-owned release carriers, on top of frozen main
d0f53933f5c1ddd7953fd86eb203227236217084. The cut ran on Deno 2.9.7 withDENO_V8_FLAGS=--max-old-space-size=4096. The original cut contained no source or test logic changes. A follow-up repairs only unpublished-release fixture resolution; all subprocesses and behavior assertions remain.The terminal candidate is 0.0.9-canary.4 on
d0f53933: release-canary 41539714417 published all 35 packages and e2e-cli-prod 41540843051 passed against those exact published packages. Therelease/canary-pairstatus is success on that content commit. Main CI 41536813111 and e2e-cli 41536868868 are also green.Refs #2474
Gate results at the cut (Deno 2.9.7)
publish:readinessok: true; all 9 checks PASS, 35 publishable workspace members, no first-publish packagesrelease:preflightpublish:dry-runSuccess Dry run completedeno ci --prodrelease:verify-canary-pairat0c97df4aed0f53933f5c1ddd7953fd86eb203227236217084; generated freshness and provenance verifiedd0f53933The cut's validations and commit completed successfully. Its initial normal push hit a transient DNS failure; the same immutable commit was resumed through normal push and PR creation under the retry policy.
Release CI fixture repair
The cut exposed two auth/SQLite consumer fixtures resolving unpublished
@netscript/config@0.0.9, and two Postgres normalizer fixtures resolving unpublished@netscript/plugin@0.0.9. Following #2388, assert the exact generated public pins before using checkout exports. The Postgres fixture prepares its committed lock for the actual Prisma config probe entrypoint, avoiding unused import-map exports. Only two test files change; shipped source, templates, dependencies, and lockfiles are unchanged.The initial shard-2 seed-watcher failure was a missing scratch parent directory; its focused tests pass without a change. Scaffold and breaking-migration cancellations were superseded by newer per-ref runs; the latest scaffold run policy-skipped and breaking-migration passed.
Deno 2.9.7: focused subprocess tests, scoped check/lint/fmt, release preflight, and review-thread gate are recorded in the release evidence. Required CI must pass at the final head before merge. A fresh canary pair will qualify the merge commit before stable publication because the verifier rejects inheriting version-only evidence through test deltas.