Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: Ducksss/codex-profiles
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.4.0
Choose a base ref
...
head repository: Ducksss/codex-profiles
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.4.1
Choose a head ref
  • 3 commits
  • 10 files changed
  • 3 contributors

Commits on Jul 1, 2026

  1. feat: add in-shell profile activation (env, use, shell-init) 

    Pin the current shell to a profile without prefixing every command:

- `env <profile> [--shell bash|zsh|fish]` prints eval-able shell code that
  exports CODEX_HOME (plus an informational CODEX_PROFILE_NAME marker for
  prompts). Uninitialized profiles warn on stderr so stdout stays eval-safe.
- `shell-init <bash|zsh|fish>` prints a shell wrapper enabling the shorter
  `use <profile>` verb; run without the wrapper, `use` prints setup guidance
  instead of failing silently.

Activation stays within the existing boundary: the tool only ever sets
CODEX_HOME. Updates usage(), the bash/zsh/fish completion generators, README,
and docs/llms.txt; adds 7 tests including a bash/zsh integration test that
sources the wrapper and confirms `use` mutates the shell.

Co-Authored-By: Claude Opus 4.8 <[email protected]>
    @Ducksss @claude
    Ducksss and claude committed Jul 1, 2026
    Configuration menu
    Copy the full SHA
    02a3ac1 View commit details
    Browse the repository at this point in the history

  2. ci: automate releases with auto patch bump on bin/** changes 

    Replace the tag-triggered publish workflow with a Release workflow that
fires on pushes to main touching bin/** (or via manual dispatch). It
auto-increments the patch version, bumps package.json/lock, the script
VERSION, and the docs version in lockstep, runs make test (so the
version-sync guard gates the release), commits, tags, publishes to npm
with provenance, and creates the GitHub Release.

The bump commit is pushed with GITHUB_TOKEN, whose pushes do not trigger
workflows, so the release cannot loop-trigger itself. A workflow_dispatch
`version` input forces a specific version (minor/major); `dry_run` builds
without publishing. Raw tag pushes no longer publish.

Co-Authored-By: Claude Opus 4.8 <[email protected]>
    @Ducksss @claude
    Ducksss and claude committed Jul 1, 2026
    Configuration menu
    Copy the full SHA
    fe5455f View commit details
    Browse the repository at this point in the history

  3. chore(release): v0.4.1

    @github-actions
    github-actions[bot] committed Jul 1, 2026
    Configuration menu
    Copy the full SHA
    4684442 View commit details
    Browse the repository at this point in the history
Loading