Release v1.2.9

[wtfsayo]

Summary

• Merging develop branch into main for v1.2.8 release
• Includes all recent fixes and improvements

Changes

• Fixed incorrect publish scripts in test-utils and plugin-starter packages that were causing CI failures
• All other changes from develop branch

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch develop

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai auto-generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[claude]

Claude finished @wtfsayo's task —— View job

---

PR Review Complete ✅

• Read changed files to understand modifications
• Verify release PR appropriateness
• Check for critical issues
• Provide review feedback

---

Review Feedback

⚠️ IMPORTANT: Version mismatch → Fix: Update PR title/description to match

• PR title says "v1.2.9" but description says "v1.2.8"
• Package versions show "1.2.7" - ensure consistency before release

💡 SUGGESTION: Changes are appropriate → Consider: This is a clean fix

• ✅ Correctly removes elizaos publish scripts from packages/plugin-starter and packages/test-utils
• ✅ Aligns with CLAUDE.md guidance: "DO NOT USE THE elizaos CLI WITHIN THE eliza MONOREPO ITSELF"
• ✅ Project uses Lerna for publishing (root package.json:27-28), not individual package scripts
• ✅ No security, typing, or tooling issues
• ✅ No tests needed for configuration cleanup

Release PR Structure: ✅ Clean merge from develop to main with appropriate CI fixes

[claude]

Claude finished @wtfsayo's task —— View job

---

📋 PR Review - Release v1.2.9

Todo List:

• Read changed files to understand what was removed
• Analyze changes against security, testing, and tool requirements
• Provide review feedback in specified format

---

Review Analysis

This is a retrospective review of a merged release PR that removed problematic publish scripts from two packages.

Changes Made:

• packages/plugin-starter/package.json: Removed 1 line (likely a problematic publish script)
• packages/test-utils/package.json: Removed 1 line (likely a problematic publish script)

Key Findings:

💡 CONTEXT: Version discrepancy between PR title (v1.2.9) and body (v1.2.8) - Consider aligning version references

✅ PUBLISHING ARCHITECTURE: The changes align with proper monorepo publishing strategy:

• plugin-starter correctly marked as "private": true (template package)
• test-utils properly configured for publishing (has publishConfig, no private flag)
• Lerna handles publishing with --no-private --force-publish flags

✅ TOOL COMPLIANCE: All scripts use bun commands (no npm/yarn/pnpm violations)

✅ SECURITY: No hardcoded secrets or security issues detected

✅ MONOREPO STANDARDS:

• Uses @elizaos/core imports correctly
• Follows workspace dependency pattern (workspace:*)
• Proper TypeScript configuration

Assessment:

The removed publish scripts were likely causing CI failures because individual packages shouldn't have their own publish scripts in a Lerna-managed monorepo. This fix ensures publishing is handled centrally by the monorepo tooling.

Overall: ✅ APPROVED - Clean fix that resolved CI issues by removing incorrect publish scripts while maintaining proper publishing configuration.

---