Skip to content

release: Release v0.1.4#5

Merged
pedronauck merged 2 commits into
mainfrom
release/v0.1.4
May 13, 2026
Merged

release: Release v0.1.4#5
pedronauck merged 2 commits into
mainfrom
release/v0.1.4

Conversation

@pedronauck
Copy link
Copy Markdown
Member

@pedronauck pedronauck commented May 5, 2026

Release v0.1.4

This PR prepares the release of version v0.1.4.

Changelog

0.1.4 - 2026-05-12

Documentation

  • Ledger

Features

  • Codex loop skill

Release Notes

Features

Built-in codex-loop tracking skill

codex-loop install now ships and refreshes a bundled codex-loop skill at
${CODEX_HOME:-$HOME/.codex}/skills/codex-loop/, and new runtime configs
default to optional_skill_name = "codex-loop" so every automatic
continuation names the managed skill without needing a workspace path.

What you get out of the box:

  • A restart-safe tracking lane that bootstraps .codex/loop/<name>/ with
    request.md, state.json, per-task files under tasks/, and
    per-iteration memory under memory/.
  • Stdlib-only helper scripts (init-tracking.py, detect-next.py,
    update-tracking.py, validate-tracking.py) for deterministic task,
    blocker, verification, and history transitions.
  • Continuation and goal prompts that now honor optional_skill_name even
    when no optional_skill_path is configured, so the name-only default
    resolves as a normal Codex skill.

Install/uninstall safety:

  • codex-loop install migrates existing configs from a missing or blank
    optional_skill_name to "codex-loop" while preserving any non-empty
    custom value.
  • The managed skill copy is refreshed on every install via atomic writes.
  • A .codex-loop-managed marker gates the directory: install refuses to
    overwrite an unmanaged skills/codex-loop/, and codex-loop uninstall
    only removes the directory when that marker is present.

Summary by CodeRabbit

  • Chores
    • Updated plugin version.

Review Change Stack

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 5, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 010fe435-1f49-439b-b386-c228ac054149

📥 Commits

Reviewing files that changed from the base of the PR and between d506989 and 2a0da35.

⛔ Files ignored due to path filters (4)
  • .release-notes/archive/v0.1.4/built-in-codex-loop-tracking-skill-1778606910.md is excluded by !**/*.md
  • CHANGELOG.md is excluded by !**/*.md
  • RELEASE_BODY.md is excluded by !**/*.md
  • RELEASE_NOTES.md is excluded by !**/*.md
📒 Files selected for processing (1)
  • plugins/codex-loop/.codex-plugin/plugin.json

Walkthrough

The plugin manifest version for codex-loop is incremented from 0.1.3 to 0.1.4 in the plugin configuration file.

Changes

Plugin Version Bump

Layer / File(s) Summary
Manifest Version
plugins/codex-loop/.codex-plugin/plugin.json
Version field updated from 0.1.3 to 0.1.4.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • compozy/codex-loop#3: Both PRs modify the same manifest file updating the "version" field.
  • compozy/codex-loop#4: Both PRs bump the plugin manifest version field sequentially (0.1.2→0.1.3 and 0.1.3→0.1.4).

Poem

🐰 One point four, a tiny hop,
A whisper in the plugin's clock,
Numbers tick, release bells chime,
A small change keeps the rhythm fine,
Hooray — the loop continues on!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main change in the changeset - a version bump from 0.1.3 to 0.1.4 for a release.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release/v0.1.4

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 5, 2026

✅ Dry-Run Completed Successfully

📊 Build Summary

  • Version: 0.0.0-1777998317
  • Commit: 5010e1c

📦 Built Artifacts

Not available.


This is an automated comment from the release dry-run check.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 5, 2026

✅ Dry-Run Completed Successfully

📊 Build Summary

  • Version: 0.0.0-1777998317
  • Commit: d506989

📦 Built Artifacts

Not available.


This is an automated comment from the release dry-run check.

@github-actions
Copy link
Copy Markdown
Contributor

✅ Dry-Run Completed Successfully

📊 Build Summary

  • Version: 0.0.0-1778607094
  • Commit: 2a0da35

📦 Built Artifacts

Not available.


This is an automated comment from the release dry-run check.

@pedronauck pedronauck merged commit 305a50d into main May 13, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant