Default compilation to local output and publish latest - #35
Merged
Merged
Conversation
Compile into the current folder unless --github is selected. Keep the existing output safety and retained-work recovery, and use a new minor line for the changed default. Publish approved versions directly to latest using the existing green main CI run. Keep source, package, environment, and provenance checks without repeating tests or npm account ceremonies during publication.
raghubetina
force-pushed
the
codex/local-first-release-20260922
branch
from
September 22, 2026 20:22
d204b98 to
d94f530
Compare
raghubetina
marked this pull request as ready for review
September 22, 2026 20:23
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
1 participant
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.
firstdraft plan compilenow writes the generated application into the current folder. The existing GitHub Publication path requires--github, and explicit--outputpaths remain supported. CLI 0.4.0 records the changed default.Package publication selects
latestdirectly and reuses successful CI for the selected main commit. The protected tag, environment approval, package checks, OIDC, and provenance remain in place. The release guide uses the existing coordinated approval and relevant local smoke evidence.Validation: 199 tests, typecheck, lint, formatting, package inventory, and packed HTTP smoke passed. The standard GitHub CLI lookup found existing successful main CI. The release workflow has not published a package from this change.