chore: release dev

[JayGhiya]

🤖 I have created a release beep boop

code-confluence-flow-bridge: 0.78.0

0.78.0 (2026-04-29)

Features

• search-backend-temporal: move from opensearch to postgresql for basic workflow search operations to reduce memory footprint by ~700-900 mb (9ea5d67)

Bug Fixes

• flow-bridge: use Any type for workflow interceptor return types (eee7c97)

unoplat-code-confluence-frontend: 1.54.0

1.54.0 (2026-04-29)

Features

• agent-events: anchor-based scroll restoration for older history via imperative handle (c59cdd5)

Bug Fixes

• agent-events-utils: always skip tool.result events in display item building (c1727cb)
• frontend: use useLayoutEffect for scroll snap reset on codebase change (5fb9b4a)

---

This PR was generated with Release Please. See documentation.

[coderabbitai]

Warning

Rate limit exceeded

@JayGhiya has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 55 minutes and 18 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 170dbf9f-f094-46f1-8dc9-e0068aa2a8ab

📥 Commits

Reviewing files that changed from the base of the PR and between 0e5b7ba and 674276a.

⛔ Files ignored due to path filters (1)

• unoplat-code-confluence-ingestion/code-confluence-flow-bridge/uv.lock is excluded by !**/*.lock

📒 Files selected for processing (5)

• .github/configuration/release-please-manifest.json
• unoplat-code-confluence-frontend/CHANGELOG.md
• unoplat-code-confluence-frontend/package.json
• unoplat-code-confluence-ingestion/code-confluence-flow-bridge/CHANGELOG.md
• unoplat-code-confluence-ingestion/code-confluence-flow-bridge/pyproject.toml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release-please--branches--dev

---

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

_{Review rate limit: 0/1 reviews remaining, refill in 55 minutes and 18 seconds.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[claude]

Claude finished @JayGhiya's task —— View job

---

PR Review Analysis

Todo List:

• Read and analyze changed files
• Review changelog entries for accuracy
• Check version bumps and semantic versioning compliance
• Assess for potential issues or concerns
• Provide comprehensive review feedback

Code Review Summary

This is a release PR generated by release-please automation. Overall, this appears to be a standard, well-structured release with appropriate version bumps and changelog entries.

✅ Positive Findings

Semantic Versioning Compliance

• Frontend: 1.53.0 → 1.54.0 - Correct minor version bump for new features + bug fixes
• Flow-bridge: 0.77.0 → 0.78.0 - Correct minor version bump for new features + bug fixes

Changelog Quality

• Well-structured conventional commit format
• Clear categorization of features vs bug fixes
• Proper commit hash references for traceability
• Descriptive commit messages that explain the "what" and "why"

Release Structure

• Release manifest properly updated (/.github/configuration/release-please-manifest.json:6-7)
• Package versions correctly synchronized across package.json and pyproject.toml
• No unexpected file modifications outside of version bumps

🔍 Detailed Analysis

Frontend Changes (v1.54.0)

Features:

• Scroll restoration improvements for agent events - good UX enhancement
• Uses imperative handles for anchor-based restoration - appropriate React pattern

Bug Fixes:

• Event filtering improvements (tool.result events) - prevents UI noise
• Layout effect usage for scroll snap reset - correct hook choice for DOM synchronization

Flow-bridge Changes (v0.78.0)

Features:

• PostgreSQL Migration: Major architectural improvement moving from OpenSearch to PostgreSQL
  • Performance Impact: ~700-900MB memory reduction is significant
  • Simplification: Reduces infrastructure complexity
  • Consideration: Ensure search performance is acceptable with PostgreSQL vs dedicated search engine

Bug Fixes:

• Type safety improvement using Any for workflow interceptors - pragmatic solution for complex typing scenarios

🚨 Areas of Consideration

Performance & Architecture

1. PostgreSQL Search Migration: While memory reduction is excellent, monitor search query performance compared to OpenSearch, especially for complex queries or large datasets.

2. Frontend Scroll Handling: Multiple scroll-related changes suggest this was a problematic area. Consider adding automated tests for scroll behavior.

Type Safety

• Using Any type in flow-bridge reduces type safety. While sometimes necessary, consider if more specific union types could be used instead.

🔒 Security Assessment

• No security concerns identified
• Standard dependency versions within expected ranges
• No exposed secrets or sensitive information

🧪 Test Coverage

• Limitation: Cannot assess test coverage from release files alone
• Recommendation: Ensure the PostgreSQL migration includes comprehensive integration tests
• Recommendation: Add E2E tests for scroll restoration features

✅ Final Recommendation

APPROVE - This is a well-executed release with:

• Proper semantic versioning
• Clear, well-documented changes
• Significant performance improvements
• No critical security or quality issues

The PostgreSQL migration represents a meaningful architectural improvement that should provide better resource utilization while maintaining functionality.

---

[claude]

Claude finished @JayGhiya's task —— View job

---

PR Review Analysis

Todo List:

• Read and analyze changed files
• Review changelog entries for accuracy
• Check version bumps and semantic versioning compliance
• Assess for potential issues or concerns
• Provide comprehensive review feedback

Release PR Review: v0.78.0 + v1.54.0

✅ Code Quality & Standards

This is an automated release PR generated by release-please, which means it follows established release automation practices. The changes are limited to version bumps, changelog updates, and lock file refreshes.

✅ Semantic Versioning Compliance

Frontend (1.53.0 → 1.54.0):

• MINOR bump is correct for the feature addition
• Features: Anchor-based scroll restoration via imperative handle
• Bug fixes: Tool result event skipping, useLayoutEffect for scroll snap reset

Flow Bridge (0.77.0 → 0.78.0):

• MINOR bump is correct for the significant feature addition
• Feature: PostgreSQL migration for search operations (major architectural change)
• Bug fix: Any type usage for workflow interceptor return types

✅ Performance Considerations

Significant Performance Improvement:

• The PostgreSQL migration (commit 9ea5d67) reduces memory footprint by ~700-900 MB
• This is a substantial optimization moving from OpenSearch to PostgreSQL for basic workflow operations
• Frontend scroll optimizations using useLayoutEffect improve UI responsiveness

✅ Security Assessment

• No security-sensitive changes detected
• Standard dependency version bumps in lock files
• No introduction of new external dependencies or configuration changes

⚠️ Areas of Attention

1. Database Migration Impact: The PostgreSQL migration is a significant architectural change that should be thoroughly tested in staging environments before production deployment.

2. Type Safety Concern: The flow-bridge fix using Any type (commit eee7c97) reduces type safety. While this may be necessary for workflow interceptor flexibility, consider if more specific union types could be used instead.

3. Lock File Updates: The UV lock file shows dependency refreshes, which is normal for releases but should be validated that no unexpected version jumps occurred.

✅ Test Coverage

This is an automated release PR focused on version management. The underlying commits should have been tested individually before being included in the release.

✅ Release Process Integrity

• Changelog entries accurately reflect the commits included
• Version bumps follow semantic versioning correctly
• Release manifest properly updated
• Package.json and pyproject.toml versions synchronized

🎯 Recommendations

1. Pre-deployment: Ensure the PostgreSQL migration has been thoroughly tested with realistic data volumes
2. Monitoring: Set up alerts for memory usage post-deployment to validate the expected 700-900 MB reduction
3. Type Safety: Consider filing a follow-up task to improve type safety for workflow interceptor return types
4. Documentation: Update deployment guides if the PostgreSQL migration requires infrastructure changes

✅ Overall Assessment

This release PR is well-structured and follows proper release management practices. The changes represent meaningful improvements, particularly the significant memory optimization. The release is ready for deployment with appropriate testing of the database migration changes.

---

[JayGhiya]

🤖 Created releases:

• code-confluence-flow-bridge-v0.78.0
• unoplat-code-confluence-frontend-v1.54.0

🌻