Skip to content

Release 0.1.43#102

Merged
tkellogg merged 1 commit into
mainfrom
strix/release-0.1.43
May 10, 2026
Merged

Release 0.1.43#102
tkellogg merged 1 commit into
mainfrom
strix/release-0.1.43

Conversation

@strix-tkellogg
Copy link
Copy Markdown
Collaborator

@strix-tkellogg strix-tkellogg commented Apr 25, 2026

v0.1.43 — 2026-05-10

Release notes now live in CHANGELOG.md. Headline: the new patterns builtin skill, plus async shell jobs, ops dashboard, and a long list of fixes.

What this PR does

What this PR does NOT do

  • No pyproject.toml version bump. The Stable Release workflow rewrites the version itself based on the version input, so a manual bump on main is unnecessary.

Release process

After merge, trigger the Stable Release workflow_dispatch in .github/workflows/release.yml with version: 0.1.43. The workflow runs the test suite, rewrites pyproject.toml, builds, and publishes to PyPI.

🤖 Generated with Claude Code

Comment thread pyproject.toml Outdated
[project]
name = "open-strix"
version = "0.1.42"
version = "0.1.43"
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@strix-tkellogg can you back out this change, because the release pipeline does it already. But take the release notes and put them into a CHANGELOG.md file or release history file, whatever

@chrispatil
Copy link
Copy Markdown
Contributor

Is there an anticipated timeline for unblocking 0.1.43? Been hand-rolling skills for failure modes (silent sends, repetition loops, prose-heavy journals) that the new patterns skill — circuit-breaker, try-harder, journal-as-breadcrumbs — covers directly.

Lifts the v0.1.43 release notes out of PR #102's body and into a
CHANGELOG.md file at the repo root, in Keep a Changelog format. Adds
coverage of merged work since the PR was opened: patterns skill
(promoted to headline) plus #104 (long-running-jobs rewrite around
shell async_mode), #105/#106 (patterns description + first-read
feedback), #110 (inline SVG in web UI). Drops the manual pyproject
version bump — the release workflow rewrites the version itself.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@strix-tkellogg strix-tkellogg force-pushed the strix/release-0.1.43 branch from f7e2d19 to 4a829c6 Compare May 10, 2026 01:10
@tkellogg
Copy link
Copy Markdown
Owner

@tkellogg — both review asks done in 4a829c6:

  • Backed out the pyproject.toml version bump (force-push of the branch)
  • Lifted release notes into CHANGELOG.md at repo root, Keep-a-Changelog format

Notes also expanded to cover PRs that merged after this one was opened: #104 (long-running-jobs rewrite), #105 / #106 (patterns), #110 (inline SVG). The patterns skill is promoted to the top of the file as the headline feature — that's the thing chrispatil is asking about over on #102 (comment).

PR body has been replaced with a short pointer; the canonical notes are the file. Ready for re-review.

@tkellogg tkellogg merged commit 70e2d54 into main May 10, 2026
@tkellogg tkellogg deleted the strix/release-0.1.43 branch May 10, 2026 01:13
@tkellogg
Copy link
Copy Markdown
Owner

@chrispatil — 0.1.43 is live: https://pypi.org/project/open-strix/0.1.43/ · https://github.com/tkellogg/open-strix/releases/tag/v0.1.43

pip install -U open-strix (or uv add open-strix@0.1.43) and you'll get the patterns skill on disk under open_strix/builtin_skills/patterns/. The three sub-skills directly map to what you described:

  • circuit-breaker — repetition-loop detection (cuts the cycle before more tokens spend)
  • try-harder — silent-send recovery (verifies side-effects after tool calls instead of trusting the "sent" return)
  • journal-as-breadcrumbs — terse breadcrumb format (replaces prose-heavy state narration)

Plus #110's inline-SVG attachment story for the web UI if you're using that path. Full notes: CHANGELOG.md.

Thanks for the nudge — that comment is what pulled the PR over the line.

@chrispatil
Copy link
Copy Markdown
Contributor

Thanks Tim! 0.1.43 installed clean. Staying observational for a few days to see how patterns/messaging handles the silent-send pattern in real conversation. Looking forward to poking at /ops once we're past verification. Will report back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants