chore: release dev

[JayGhiya]

🤖 I have created a release beep boop

code-confluence-flow-bridge: 0.75.1

0.75.1 (2026-04-12)

Bug Fixes

• common-version-ingestion: upgrade commons dependency to v0.47.0 (6b722d9)

unoplat-code-confluence-query-engine: 0.40.1

0.40.1 (2026-04-12)

Bug Fixes

• common-version-query-engine: upgrade commons dependency to v0.47.0 (c7844d4)

---

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 23 minutes and 36 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 23 minutes and 36 seconds.

⌛ 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: d726b0f8-f697-4af2-bd74-2042517f2bd2

📥 Commits

Reviewing files that changed from the base of the PR and between 3c390ef and 57c682b.

⛔ Files ignored due to path filters (2)

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

📒 Files selected for processing (5)

• .github/configuration/release-please-manifest.json
• unoplat-code-confluence-ingestion/code-confluence-flow-bridge/CHANGELOG.md
• unoplat-code-confluence-ingestion/code-confluence-flow-bridge/pyproject.toml
• unoplat-code-confluence-query-engine/CHANGELOG.md
• unoplat-code-confluence-query-engine/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

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

[claude]

Claude finished @JayGhiya's task —— View job

---

PR Review Completed ✅

I've reviewed this release PR and analyzed all the changed files. Here's my comprehensive feedback:

Todo List:

• Read and analyze all changed files
• Review version bump changes and manifest updates
• Verify changelog entries accuracy
• Check dependency upgrade implications
• Assess release process adherence to best practices
• Provide comprehensive review feedback

---

📊 Release Summary

This is a patch release upgrading the commons dependency from v0.24.0/0.25.0 to v0.47.0 across two packages:

• code-confluence-flow-bridge: 0.75.0 → 0.75.1
• unoplat-code-confluence-query-engine: 0.40.0 → 0.40.1

✅ What's Working Well

Release Process:

• Proper use of release-please automation for consistent versioning
• Semantic versioning correctly applied (patch bumps for dependency updates)
• Changelog entries are well-formatted and include commit references
• Release manifest properly tracks version state

Dependency Management:

• Consistent git-based dependency sourcing across packages
• Both packages properly pin to the same commons version (v0.47.0)
• UV tool configuration looks properly structured

⚠️ Areas of Concern

1. Major Dependency Version Jump

• Issue: Upgrading from v0.24.0/0.25.0 to v0.47.0 is a 22-version jump that seems unusually large for a patch release
• Risk: Potential breaking changes or compatibility issues despite being marked as a "bug fix"
• Recommendation: Consider reviewing the commons changelog between these versions to ensure no breaking changes were introduced

2. Missing Test Coverage Validation

• Issue: No evidence that tests were run to validate the dependency upgrade
• Risk: Compatibility issues may not be detected until runtime
• Recommendation: Ensure CI tests pass before merging this release

3. Inconsistent Minimum Commons Versions

In flow-bridge/pyproject.toml:66:

unoplat-code-confluence-commons = { git = "...", rev = "unoplat-code-confluence-commons-v0.47.0" }

But dependency constraint on line 17:

"unoplat-code-confluence-commons>=0.24.0"

In query-engine/pyproject.toml:57:

unoplat-code-confluence-commons = { git = "...", rev = "unoplat-code-confluence-commons-v0.47.0" }

But dependency constraint on line 23:

"unoplat-code-confluence-commons>=0.25.0"

• Issue: The minimum version constraints haven't been updated to reflect the new v0.47.0 requirement
• Risk: Future dependency resolution could potentially install an older incompatible version
• Recommendation: Update the minimum version constraints to >=0.47.0 in both files

🔒 Security Assessment

• ✅ No sensitive information exposed
• ✅ Git dependency sources use proper commit pinning
• ✅ No hardcoded credentials or secrets detected

⚡ Performance Considerations

• Git-based dependencies are properly pinned to specific revisions, ensuring reproducible builds
• No performance-related concerns identified in the version changes

📋 Additional Recommendations

1. Update Version Constraints: Fix the minimum version requirements as noted above
2. Validate Compatibility: Ensure all tests pass with the new commons version
3. Release Notes: Consider documenting what specific fixes/improvements this commons upgrade brings
4. Gradual Updates: For future major version jumps, consider smaller incremental updates to reduce risk

📝 Files Reviewed

• .github/configuration/release-please-manifest.json:4,6 - Version tracking ✅
• unoplat-code-confluence-ingestion/code-confluence-flow-bridge/pyproject.toml:3,66 - Version and dependency updates ⚠️
• unoplat-code-confluence-query-engine/pyproject.toml:3,57 - Version and dependency updates ⚠️
• Both CHANGELOG.md files - Release notes ✅

Overall Assessment: This is a well-structured automated release, but the dependency version constraints should be updated to match the actual pinned versions to prevent future compatibility issues.

---

[claude]

Claude finished @JayGhiya's task —— View job

---

PR Review Complete ✅

I've completed my review of this release PR. Here's my comprehensive feedback:

Todo List:

• Read and analyze all changed files
• Review version bump changes and manifest updates
• Verify changelog entries accuracy
• Check dependency upgrade implications
• Assess release process adherence to best practices
• Provide comprehensive review feedback

---

🔍 Review Summary

This is a clean release PR generated by Release Please that bumps patch versions for two packages following a commons dependency upgrade. Overall, the release follows good practices with proper semantic versioning and clear changelog entries.

✅ Code Quality & Best Practices

Excellent:

• Proper semantic versioning: patch bumps (0.75.0→0.75.1, 0.40.0→0.40.1) for dependency upgrades
• Consistent changelog format with clear categorization under "Bug Fixes"
• Automated release process using Release Please reduces human error
• Git tag references pointing to specific commits for reproducibility

Good:

• Both packages use pinned git references (rev = "unoplat-code-confluence-commons-v0.47.0") instead of branch names for dependency sourcing
• Lockfiles are properly updated to reflect the new dependency versions

🔧 Technical Analysis

Dependency Upgrade:

• Both packages upgrade unoplat-code-confluence-commons from local versions to v0.47.0
• Query engine: minimum version constraint bumped from >=0.25.0 to >=0.25.0 (dependency source changed to git tag)
• Flow bridge: minimum version constraint stays at >=0.24.0 (dependency source changed to git tag)

Version Consistency:

• Release manifest correctly updated: flow-bridge to 0.75.1, query-engine to 0.40.1
• Package versions in pyproject.toml files match the release manifest ✅

🚨 Minor Observations

Inconsistent minimum version constraints:

• Query engine requires >=0.25.0 but uses v0.47.0 (22 versions gap)
• Flow bridge requires >=0.24.0 but uses v0.47.0 (23 versions gap)
• Recommendation: Consider updating minimum version requirements to match the pinned version for clarity

🔒 Security & Performance

• Security: No security concerns - this is a dependency upgrade with pinned versions
• Performance: No performance implications visible in this release
• Dependencies: Using git tag references instead of branch names improves supply chain security

🧪 Test Coverage

• No test changes in this PR (expected for dependency upgrades)
• Lockfile updates suggest dependency resolution was successful
• Assumption: CI/CD pipeline validates compatibility before release

📋 Release Process Adherence

Excellent compliance with release best practices:

• ✅ Automated changelog generation
• ✅ Proper commit message formatting with scope prefixes
• ✅ Linked commit SHAs in changelogs
• ✅ Semantic versioning compliance
• ✅ Clean git history with meaningful commit messages

🎯 Final Recommendation

APPROVE - This is a well-executed release PR that follows all best practices. The dependency upgrade appears safe and follows proper semantic versioning. No blocking issues identified.

Optional enhancement: Consider aligning minimum dependency version constraints with actual pinned versions for better dependency management clarity.

---

[JayGhiya]

🤖 Created releases:

• code-confluence-flow-bridge-v0.75.1
• unoplat-code-confluence-query-engine-v0.40.1

🌻