Skip to content

Co-bump persist v6.5.0 -> v6.6.0 (with_hardware_signer family floor)#111

Open
emooreatx wants to merge 1 commit into
mainfrom
persist-6.6
Open

Co-bump persist v6.5.0 -> v6.6.0 (with_hardware_signer family floor)#111
emooreatx wants to merge 1 commit into
mainfrom
persist-6.6

Conversation

@emooreatx

Copy link
Copy Markdown
Contributor

Version-only co-bump (dep + dev-dep) to persist v6.6.0 (additive — adds Engine::with_hardware_signer, CIRISPersist#220/#221). Lets a host (CIRISServer) resolve the whole graph to one persist rev on the 6.6 floor. Suggest tagging v3.3.0 so consumers (lens-core, CIRISServer) can repin from this branch to a tag. lens-core's matching co-bump rides CIRISLensCore#55.

🤖 Generated with Claude Code

Version-only across the dep + dev-dep; persist 6.6.0 is additive. Lets a host
(CIRISServer) take a TPM federation signer (Engine::with_hardware_signer, #220)
while edge + lens-core + persist resolve to one persist rev.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

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