release: v0.2.0 — TaxDiagnosticResult + fail-closed guards + README repositioning#49
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reached
More reviews will be available in 44 minutes and 10 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
📝 WalkthroughWalkthroughVersion bumped from Changesv0.2.0 Release Metadata
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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 |
Greptile SummaryThis is a release-packaging PR for v0.2.0, bumping version numbers across PyPI (
Confidence Score: 5/5Pure release-packaging change — all five files are version bumps or a CHANGELOG addition with no logic, no executable code, and no dependency changes. All changes are mechanical: four version strings updated from 0.1.0 to 0.2.0 across pyproject.toml, npm/package.json, npm/package-lock.json, and sonar-project.properties, plus a CHANGELOG entry. There is nothing here that can regress behavior — the actual feature code was merged in prior PRs. No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[PR 49 merged to main] --> B[Tag v0.2.0 on GitHub]
B --> C[PyPI publish\npython -m build && twine upload dist/*]
B --> D[npm publish\ncd npm && npm publish]
C --> E[qwed-tax 0.2.0 on PyPI]
D --> F[qwed-ai/tax 0.2.0 on npmjs.com]
E --> G[Close issue 34]
F --> G
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
A[PR 49 merged to main] --> B[Tag v0.2.0 on GitHub]
B --> C[PyPI publish\npython -m build && twine upload dist/*]
B --> D[npm publish\ncd npm && npm publish]
C --> E[qwed-tax 0.2.0 on PyPI]
D --> F[qwed-ai/tax 0.2.0 on npmjs.com]
E --> G[Close issue 34]
F --> G
Reviews (2): Last reviewed commit: "fix: sync version across package-lock.js..." | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
|
CodeRabbit (@coderabbitai) review |
✅ Action performedReview finished.
|
![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
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@npm/package.json`:
- Around line 3-4: Update the version field in package-lock.json to match the
version in package.json. Currently package.json shows version 0.2.0 while
package-lock.json still records 0.1.0. Find the version field in
package-lock.json and change it from 0.1.0 to 0.2.0 to maintain consistency
between the two files and avoid confusion for developers and deployment
processes.
In `@pyproject.toml`:
- Around line 3-4: The version in pyproject.toml has been updated to 0.2.0, but
the sonar-project.properties file still contains the old version 0.1.0 in the
sonar.projectVersion property. Update the sonar.projectVersion value in
sonar-project.properties from 0.1.0 to 0.2.0 to keep the project metadata
synchronized across configuration files.
🪄 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: 34662a10-e26c-4621-9c15-c78965143749
📒 Files selected for processing (3)
CHANGELOG.mdnpm/package.jsonpyproject.toml
… remove trailing period - Remove trailing period from pyproject.toml description (Greptile P2) - Bump package-lock.json version to 0.2.0 (CodeRabbit) - Bump sonar-project.properties version to 0.2.0 (CodeRabbit)
|
1 participant
Summary
This is the v0.2.0 release PR. It bumps version numbers across PyPI, npm, and adds the CHANGELOG entry. Merge this PR before cutting the GitHub release / tag.
Version bumps
pyproject.toml0.1.00.2.0npm/package.json0.1.00.2.0qwed_tax/__init__.py0.2.0CHANGELOG.mdAlso updated package descriptions to align with the new README positioning:
"Deterministic Verification for Payroll and Tax Compliance."→"The Verification Gate for AI-Generated Tax Decisions.""Deterministic Tax Verification for Agentic Finance (Browser/Node)"→"The Verification Gate for AI-Generated Tax Decisions"What shipped in v0.2.0
Features
TaxDiagnosticResult3-layer model (agent message / developer fields / proof ref)to_diagnostic()withbuild_trace()+RuleRefBug fixes
== Truecheck, every input passes as verified #40 — Middleware success label narrowed + ReciprocityGuard Z3 removedextra="forbid")Stats
audit.pyto_diagnostic()coverageAfter merge
v0.2.0python -m build && twine upload dist/*cd npm && npm publishSummary by CodeRabbit
Release 0.2.0
New Features
Bug Fixes
Changed