chore: V1.2.0 release - verified authorship and CI/CD hardening#79
chore: V1.2.0 release - verified authorship and CI/CD hardening#79
Conversation
github-actions
bot
added
the
documentation
|
Warning Rate limit exceeded
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 10 minutes and 1 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the 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. 📝 WalkthroughWalkthroughThis PR updates documentation, changelogs, and website files to reflect the v1.2.0 release, including GitHub OAuth author verification capabilities. All changes are version bumps and documentation updates across multiple files with no code modifications. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
iamvirul
changed the title
iamvirul
changed the title
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
ROADMAP.md (1)
294-294:⚠️ Potential issue | 🟡 Minor
Last Updatedmetadata is staleLine 294 still says
2026-03-22despite the v1.2.0 roadmap updates in this PR. Please bump it to the actual update date.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@ROADMAP.md` at line 294, Update the stale "Last Updated" metadata entry: locate the "Last Updated:" line in the ROADMAP.md file (the metadata entry that currently reads "2026-03-22") and change the date to the actual update date for this PR (replace with 2026-04-04) so the file reflects the current revision.CHANGELOG.md (1)
409-420:⚠️ Potential issue | 🟡 MinorAdd missing version comparison links.
The changelog is missing version comparison links for
[1.2.0]and[1.1.0], and the[Unreleased]link still points tov1.0.0...HEADinstead ofv1.2.0...HEAD.📎 Proposed fix to add missing version links
-[Unreleased]: https://github.com/iamvirul/deepdiff-db/compare/v1.0.0...HEAD +[Unreleased]: https://github.com/iamvirul/deepdiff-db/compare/v1.2.0...HEAD +[1.2.0]: https://github.com/iamvirul/deepdiff-db/compare/v1.1.0...v1.2.0 +[1.1.0]: https://github.com/iamvirul/deepdiff-db/compare/v1.0.0...v1.1.0 [1.0.0]: https://github.com/iamvirul/deepdiff-db/compare/v0.9...v1.0.0🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@CHANGELOG.md` around lines 409 - 420, Update the changelog release links: change the [Unreleased] comparison target from v1.0.0...HEAD to v1.2.0...HEAD, and add missing comparison links for [1.2.0] and [1.1.0] pointing to their respective GitHub compare URLs (e.g., .../compare/v1.1.0...v1.2.0 for [1.2.0] and .../compare/v1.0.0...v1.1.0 for [1.1.0]); ensure the bracketed reference names [Unreleased], [1.2.0], and [1.1.0] match exactly the tags used elsewhere in the file.
🧹 Nitpick comments (1)
ROADMAP.md (1)
210-210: Use “Released” instead of “Shipping” for consistencyLine 210 says “Shipping in v1.2.0”, while other completed items use “Released in …”. Align wording to “Released in v1.2.0 (2026-04-05)”.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@ROADMAP.md` at line 210, Update the roadmap entry for "GitHub OAuth Author Verification" to use the consistent wording "Released" instead of "Shipping" and include the release date; change the line that currently reads "Shipping in v1.2.0 (issue `#77`)" to "Released in v1.2.0 (2026-04-05) (issue `#77`)" so it matches other completed items.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@ROADMAP.md`:
- Around line 45-47: The ROADMAP lists "GitHub OAuth author verification —
device flow auth in `version init`; verified `github:<username>` used
automatically in `version commit`" under both v1.1.0 and v1.2.0; remove the
duplicate so the feature appears in only the correct release entry: decide
whether the actual shipped version is v1.1.0 or v1.2.0 and delete the duplicate
bullet from the other section (references: the exact feature string "GitHub
OAuth author verification" and the `version init`/`version commit` description).
- Around line 11-13: Update the status wording for v1.2.0 in ROADMAP.md: change
the “Released: 2026-04-05” label to a tentative phrasing such as “Planned
release: 2026-04-05” (or “Target release: 2026-04-05”) for the v1.2.0 heading so
it isn’t marked as released before the tag/ship is completed; ensure the change
touches the v1.2.0 heading text that currently reads “## Current Status: v1.2.0
— Verified Authorship & CI/CD Hardening 🎉” and its following date line.
---
Outside diff comments:
In `@CHANGELOG.md`:
- Around line 409-420: Update the changelog release links: change the
[Unreleased] comparison target from v1.0.0...HEAD to v1.2.0...HEAD, and add
missing comparison links for [1.2.0] and [1.1.0] pointing to their respective
GitHub compare URLs (e.g., .../compare/v1.1.0...v1.2.0 for [1.2.0] and
.../compare/v1.0.0...v1.1.0 for [1.1.0]); ensure the bracketed reference names
[Unreleased], [1.2.0], and [1.1.0] match exactly the tags used elsewhere in the
file.
In `@ROADMAP.md`:
- Line 294: Update the stale "Last Updated" metadata entry: locate the "Last
Updated:" line in the ROADMAP.md file (the metadata entry that currently reads
"2026-03-22") and change the date to the actual update date for this PR (replace
with 2026-04-04) so the file reflects the current revision.
---
Nitpick comments:
In `@ROADMAP.md`:
- Line 210: Update the roadmap entry for "GitHub OAuth Author Verification" to
use the consistent wording "Released" instead of "Shipping" and include the
release date; change the line that currently reads "Shipping in v1.2.0 (issue
`#77`)" to "Released in v1.2.0 (2026-04-05) (issue `#77`)" so it matches other
completed items.
🪄 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: defaults
Review profile: CHILL
Plan: Pro
Run ID: 4020203b-df2c-4c04-abe1-7df5c383d869
📒 Files selected for processing (7)
CHANGELOG.mdROADMAP.mdwebsite/docs/deployment/cicd.mdwebsite/docs/deployment/docker.mdwebsite/docs/getting-started/installation.mdwebsite/docusaurus.config.jswebsite/src/pages/index.js
- ROADMAP: clarify GitHub OAuth is a v1.2.0 feature, not v1.1.0 - ROADMAP: bump Last Updated metadata to 2026-04-05 - CHANGELOG: add v1.2.0 and v1.1.0 comparison links; fix Unreleased link to point to v1.2.0...HEAD
1 participant
Summary
[1.2.0] - 2026-04-05CHANGELOG entryv1.1.0→v1.2.0): installation guide, Docker docs, CI/CD tipsv1.1→v1.2) and homepage hero badgeTest plan
[1.2.0]entry is present with correct datev1.2v1.2.0Summary by CodeRabbit
New Features
version initnow prompts for GitHub authentication (skippable with--skip-authfor CI/CD environments)version commitautomatically sets verified author information when availableDocumentation