Skip to content

ci(examples): pin the example caller to the v1.0.0 release - #43

Open
cipherstash-agent wants to merge 1 commit into
mainfrom
claude/project-thread-y6piip
Open

cipherstash-agent wants to merge 1 commit into
mainfrom
claude/project-thread-y6piip

Conversation

@cipherstash-agent

Copy link
Copy Markdown

Requested by User · project thread

Part of #8.

This points the example caller, the file every repository copies, at 38f13f4, the merge of #41. That commit becomes v1.0.0. Until now the example pinned an old pre-release commit, which no longer matches its inputs: it lacks app-client-id and still expects the CLAUDE_REVIEW_APP_ID secret.

Before merging:

  1. A person (not cipherstash-agent) comments @cipherstash-agent review on this PR. The self-test then checks the 👀 reaction fix from fix!: let the 👀 reaction through, and name the membership App by its client ID #41 live.
  2. If that passes, create the v1.0.0 tag on 38f13f4210ddc6e81d4e8ac69011ceb1069880c6. Use a GitHub release, or run git tag v1.0.0 38f13f4 && git push origin v1.0.0. Until then, zizmor fails this PR because the version comment names a tag that doesn't exist yet.

Generated by Claude Code

Refs #8

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012Jmn7nJnwMciggj9ThhFYj
@cipherstash-agent cipherstash-agent self-assigned this Nov 20, 2026

Copy link
Copy Markdown
Author

zizmor fails as expected: claude-review.yml:52: action's hash pin has mismatched or missing version comment: points to unknown ref, because the v1.0.0 tag doesn't exist yet. It will pass on a re-run once v1.0.0 is created on 38f13f4. No code change is needed.


Generated by Claude Code

Copy link
Copy Markdown
Author

integration-test: received ready request from https://github.com/cipherstash/workflows/actions/runs/44669977628/attempts/1


Generated by Claude Code

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.

2 participants