Skip to content

feat: add persistent-tee to release and fix dispatch workflow - #57

Merged
chudkowsky merged 2 commits into
mainfrom
feat/release-persistent-tee
Mar 26, 2026
Merged

feat: add persistent-tee to release and fix dispatch workflow#57
chudkowsky merged 2 commits into
mainfrom
feat/release-persistent-tee

Conversation

@chudkowsky

Copy link
Copy Markdown
Collaborator

Summary

  • Build, archive, and upload persistent-tee on all 4 platforms alongside persistent and ops
  • Copy persistent-tee into the Docker image (docker run ghcr.io/dojoengine/saya:latest persistent-tee <args>)
  • Remove invalid readme field from sub-workspace Cargo.toml files (caused cargo release to fail)
  • Add webfactory/ssh-agent with KATANA_TEE_DEPLOY_KEY to release.yml and release-dispatch.yml for private katana-tee dependency
  • Fix --allow-dirty invalid flag in release-dispatch.yml

Test plan

  • Merge and trigger release-dispatch with 0.4.0 — confirm all sub-workspace versions bump correctly
  • Confirm release build produces persistent-tee artifacts on all platforms
  • Pull Docker image and confirm persistent-tee is at /usr/local/bin/persistent-tee

🤖 Generated with Claude Code

chudkowsky and others added 2 commits March 25, 2026 20:39
- Add webfactory/ssh-agent with KATANA_TEE_DEPLOY_KEY to release.yml
  so persistent-tee private deps can be fetched during build
- Add same SSH agent to release-dispatch.yml for cargo metadata resolution
- Add --allow-dirty to sub-workspace cargo release calls to avoid false
  positive uncommitted changes warning after root workspace is bumped

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@chudkowsky
chudkowsky merged commit 5e53460 into main Mar 26, 2026
7 checks passed
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.

1 participant