chore(codex): prepare 0.2.0 release #6

2026-11-02T03:12:06Z

eleith-gitea-agent Bot commented

2026-11-02 03:12:06 +00:00

Status

Ready for owner review and landing. No further commits are currently planned in this PR. This prepares the 0.2.0 successor release; it does not publish it.

Scope

Regenerated from landed main 3f059ea after UX PR #5, using both pending Changesets. The older pre-UX release-preparation stash was not applied and remains intact.

Exactly four tracked paths change:

Consume minor codex-controls and patch codex-ux.
Set @eleith-pi/codex from 0.1.1 to 0.2.0 and update its description for context windows, account usage and fast-mode controls.
Add both generated release entries, correct the changelog heading to the successor package name, and preserve historical entries unchanged.

No production source, README, workflow, dependency, lockfile, credential or personal installation changes.

Verification

Fresh release code and readability reviews: clear.
1,309 tests / 73 files passed.
All extension builds, lint, typecheck, formatting and whitespace checks passed.
Validated the consumed minor+patch plan directly against the resulting version and both changelog summaries; historical notes and unrelated manifest fields are unchanged. Both entries are intentionally consumed, so no artificial empty Changeset was added to satisfy the pending-entry status guard.
Fresh pnpm pack ran prepack/build after UX landed. Inspected the exact archive: LICENSE, dist/index.js, package.json, CHANGELOG.md, README.md, and no other files.
Packed manifest is @eleith-pi/codex@0.2.0 with the expected Pi entrypoint/repository/host peers, no runtime dependencies, no remaining workspace: references, and no prepack lifecycle. The private internal helper is bundled and appears only as rewritten dev metadata.
Every packed file other than the transformed manifest matches the current built/source file byte for byte. This is the new post-UX artifact, not the stale cached pre-UX tarball.

No disposable npm consumer installation test was repeated. No registry publish or interactive terminal smoke was performed during release preparation; packaging inspection is not proof of registry permission, live account behavior, or successful OIDC publication.

Release boundary

No version tag has been created, and no npm/private Gitea package has been published. Publishing workflows remain unchanged, tag-gated and version-checked; merging this PR does not trigger publication.

After this lands, manual first stable npm publication becomes the next separately authorized release operation, followed by the owner's planned package-specific trusted-publisher setup. Do not silently create a bootstrap/prerelease or change that sequence. Trust must be for the new @eleith-pi/codex package and codex.yml; predecessor package trust does not transfer. A later tag job skipping an already manually published npm version does not validate OIDC.

Owner controls landing and all release authorization. No manual npm publish command is requested by this PR.

## Status Ready for owner review and landing. **No further commits are currently planned in this PR.** This prepares the 0.2.0 successor release; it does not publish it. ## Scope Regenerated from landed main `3f059ea` after UX PR #5, using both pending Changesets. The older pre-UX release-preparation stash was not applied and remains intact. Exactly four tracked paths change: - Consume minor `codex-controls` and patch `codex-ux`. - Set `@eleith-pi/codex` from **0.1.1 to 0.2.0** and update its description for context windows, account usage and fast-mode controls. - Add both generated release entries, correct the changelog heading to the successor package name, and preserve historical entries unchanged. No production source, README, workflow, dependency, lockfile, credential or personal installation changes. ## Verification - Fresh release code and readability reviews: **clear**. - **1,309 tests / 73 files passed**. - All extension builds, lint, typecheck, formatting and whitespace checks passed. - Validated the consumed minor+patch plan directly against the resulting version and both changelog summaries; historical notes and unrelated manifest fields are unchanged. Both entries are intentionally consumed, so no artificial empty Changeset was added to satisfy the pending-entry status guard. - Fresh `pnpm pack` ran prepack/build after UX landed. Inspected the exact archive: **LICENSE, dist/index.js, package.json, CHANGELOG.md, README.md**, and no other files. - Packed manifest is **@eleith-pi/codex@0.2.0** with the expected Pi entrypoint/repository/host peers, no runtime dependencies, no remaining `workspace:` references, and no prepack lifecycle. The private internal helper is bundled and appears only as rewritten dev metadata. - Every packed file other than the transformed manifest matches the current built/source file byte for byte. This is the new post-UX artifact, not the stale cached pre-UX tarball. No disposable npm consumer installation test was repeated. No registry publish or interactive terminal smoke was performed during release preparation; packaging inspection is not proof of registry permission, live account behavior, or successful OIDC publication. ## Release boundary No version tag has been created, and no npm/private Gitea package has been published. Publishing workflows remain unchanged, tag-gated and version-checked; merging this PR does not trigger publication. After this lands, manual first stable npm publication becomes the next separately authorized release operation, followed by the owner's planned package-specific trusted-publisher setup. Do not silently create a bootstrap/prerelease or change that sequence. Trust must be for the new `@eleith-pi/codex` package and `codex.yml`; predecessor package trust does not transfer. A later tag job skipping an already manually published npm version does not validate OIDC. Owner controls landing and all release authorization. No manual npm publish command is requested by this PR.

eleith-gitea-agent Bot added 1 commit 2026-11-02 03:12:06 +00:00

chore(codex): prepare 0.2.0 release

ci/woodpecker/pr/codex Pipeline was successful

Details

ci/woodpecker/push/codex Pipeline was successful

Details

ci/woodpecker/tag/codex Pipeline was successful

Details

1e6fbd101f

Consume the landed controls and UX Changesets, update the package description, and record both release entries under the successor package name. Preserve historical releases and leave publication to a separately authorized operation.

eleith merged commit 1e6fbd101f into main

2026-11-02 03:22:09 +00:00

eleith deleted branch chore/codex-release

2026-11-02 03:22:09 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: eleith/pi-extensions#6