chore: release main - #80
Conversation
|
Warning Review limit reachedNext included review available in 17 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
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. Comment |
There was a problem hiding this comment.
This automated release PR correctly bumps versions for both extended-data (8.5.1 → 8.5.2) and pytest-extended-data (0.2.0 → 0.2.1). All version numbers are consistent across manifest and project files, changelog entries are properly formatted, and no blocking issues were identified. The PR is ready to merge.
You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.
|
🤖 Created releases: 🌻 |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 21282b6294
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| * harden path validation and consumer guides ([8a83bd9](https://github.com/jbcom/extended-data/commit/8a83bd9e48cd77a6c3679e56eb9e994c71d2acb1)) | ||
| * harden path validation and consumer guides ([4768053](https://github.com/jbcom/extended-data/commit/47680537232e2460a583fde5d8ea136561249eb8)) |
There was a problem hiding this comment.
Remove duplicate release-note entries
These two entries describe the same change: 8a83bd9 is the merge commit whose second parent is 4768053, and its resulting tree is identical to that parent. Publishing both makes one fix appear as two independent fixes; the same duplication is also present in packages/pytest-extended-data/CHANGELOG.md. Keep only one entry, or adjust the release-note generation to deduplicate merge commits and their merged conventional commits.
Useful? React with 👍 / 👎.
🤖 I have created a release beep boop
extended-data: 8.5.2
8.5.2 (2026-08-24)
Bug Fixes
pytest-extended-data: 0.2.1
0.2.1 (2026-08-24)
Bug Fixes
This PR was generated with Release Please. See documentation.