chore: Update skill and operator package version#232
Conversation
WalkthroughThe guardian-operator-client package version is bumped from 0.14.3 to 0.14.6, and it is formally integrated into the release automation workflow. New endpoint documentation covers account snapshots and cross-account feed pagination with practical examples. ChangesGuardian Operator Client Release and Documentation
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.agents/skills/release-guardian-sdk-packages/SKILL.md:
- Around line 98-103: The command blocks in SKILL.md use sequential relative cd
commands which break if pasted together; update each package installation line
(the bash snippets under SKILL.md around the shown blocks) so each step is
execution-safe by running the cd and npm install in a subshell or otherwise
resetting to repo root (e.g., use (cd packages/guardian-client && npm install
--package-lock-only) style for the lines that currently contain "cd packages/...
&& npm install --package-lock-only"), and apply the same change to the other
affected blocks referenced (around lines 118-127 and 138-143) so every command
can be run independently from any current directory.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 9ad9b0be-3e44-4179-aa75-899611a073a6
⛔ Files ignored due to path filters (1)
packages/guardian-operator-client/package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (3)
.agents/skills/release-guardian-sdk-packages/SKILL.mdpackages/guardian-operator-client/README.mdpackages/guardian-operator-client/package.json
| ```bash | ||
| cd packages/guardian-client && npm install --package-lock-only | ||
| cd packages/guardian-evm-client && npm install --package-lock-only | ||
| cd packages/miden-multisig-client && npm install --package-lock-only | ||
| cd packages/guardian-operator-client && npm install --package-lock-only | ||
| ``` |
There was a problem hiding this comment.
Make command blocks execution-safe from any current directory.
Line 99 onward uses sequential relative cd commands; after the first cd, later paths can break when copy-pasted in one shell. Wrap each step in a subshell (or reset to repo root) so every command is independently runnable.
Suggested patch
-cd packages/guardian-client && npm install --package-lock-only
-cd packages/guardian-evm-client && npm install --package-lock-only
-cd packages/miden-multisig-client && npm install --package-lock-only
-cd packages/guardian-operator-client && npm install --package-lock-only
+(cd packages/guardian-client && npm install --package-lock-only)
+(cd packages/guardian-evm-client && npm install --package-lock-only)
+(cd packages/miden-multisig-client && npm install --package-lock-only)
+(cd packages/guardian-operator-client && npm install --package-lock-only)-cd packages/guardian-client && npm test
-cd packages/guardian-client && npm run build
-cd packages/guardian-evm-client && npm test
-cd packages/guardian-evm-client && npm run build
-cd packages/miden-multisig-client && npm test
-cd packages/miden-multisig-client && npm run build
-cd packages/guardian-operator-client && npm test
-cd packages/guardian-operator-client && npm run build
+(cd packages/guardian-client && npm test)
+(cd packages/guardian-client && npm run build)
+(cd packages/guardian-evm-client && npm test)
+(cd packages/guardian-evm-client && npm run build)
+(cd packages/miden-multisig-client && npm test)
+(cd packages/miden-multisig-client && npm run build)
+(cd packages/guardian-operator-client && npm test)
+(cd packages/guardian-operator-client && npm run build)-cd packages/guardian-client && npm publish --access public --dry-run
-cd packages/guardian-evm-client && npm publish --access public --dry-run
-cd packages/miden-multisig-client && npm publish --access public --dry-run
-cd packages/guardian-operator-client && npm publish --access public --dry-run
+(cd packages/guardian-client && npm publish --access public --dry-run)
+(cd packages/guardian-evm-client && npm publish --access public --dry-run)
+(cd packages/miden-multisig-client && npm publish --access public --dry-run)
+(cd packages/guardian-operator-client && npm publish --access public --dry-run)Also applies to: 118-127, 138-143
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In @.agents/skills/release-guardian-sdk-packages/SKILL.md around lines 98 - 103,
The command blocks in SKILL.md use sequential relative cd commands which break
if pasted together; update each package installation line (the bash snippets
under SKILL.md around the shown blocks) so each step is execution-safe by
running the cd and npm install in a subshell or otherwise resetting to repo root
(e.g., use (cd packages/guardian-client && npm install --package-lock-only)
style for the lines that currently contain "cd packages/... && npm install
--package-lock-only"), and apply the same change to the other affected blocks
referenced (around lines 118-127 and 138-143) so every command can be run
independently from any current directory.
There was a problem hiding this comment.
Pull request overview
Updates the @openzeppelin/guardian-operator-client package version from 0.14.3 to 0.14.6 (with matching lockfile bump), adds README documentation for several new client methods, and registers the operator client in the release skill checklist so future coordinated releases include it.
Changes:
- Bump
guardian-operator-clientversion to 0.14.6 inpackage.jsonandpackage-lock.json. - Document
getAccountSnapshot,listGlobalDeltas, andlistGlobalProposalsin the package README. - Add the operator client to the release-skill source-of-truth list, version bump list, lockfile refresh, test/build, dry-run, and publish-order sections.
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| packages/guardian-operator-client/README.md | Adds usage examples for three new client methods. |
| packages/guardian-operator-client/package.json | Bumps version to 0.14.6. |
| packages/guardian-operator-client/package-lock.json | Mirrors version bump in lockfile. |
| .agents/skills/release-guardian-sdk-packages/SKILL.md | Registers operator client across all release-skill steps. |
Files not reviewed (1)
- packages/guardian-operator-client/package-lock.json: Language not supported
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #232 +/- ##
=======================================
Coverage 73.18% 73.18%
=======================================
Files 122 122
Lines 21565 21565
=======================================
Hits 15782 15782
Misses 5783 5783 Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
This PR updates operator package/readme versions and skill for publishing packages.
Summary by CodeRabbit
Documentation
Chores