Skip to content

uphold 1.1.0 - #8

Merged
HackingGate merged 1 commit into
mainfrom
release/v1.1.0
Aug 12, 2026
Merged

uphold 1.1.0#8
HackingGate merged 1 commit into
mainfrom
release/v1.1.0

Conversation

@HackingGate

Copy link
Copy Markdown
Owner

Version bump and the pins in the install instructions. The two changes it carries are in #7: the shim runs a command nothing here declares, and the publication audit prunes its own fetch destination.

Consumers pin v1.0.0 today, which predates the four seam fixes merged since. Tagging this is what lets the fleet move.

…his forge

The install instructions in this file described something that did not
work: a link named for a command, on PATH for the whole machine, against
a declaration that lives in one repository's policy. Every directory
without one -- which is most of them, and every repository that declares
a shim for a different command -- got exit 2 instead of the command. The
seam now runs the command where nothing here stands in front of it, which
is what makes the documented install true.

`audit --for-publication` no longer walks pull refs the forge stopped
serving, so its report is about the repository being published rather
than about whatever this clone once fetched.
@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@HackingGate, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 52 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

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, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: ff5d5115-9dfb-4793-8a99-9638d88cb111

📥 Commits

Reviewing files that changed from the base of the PR and between 805e9d3 and 1bed66b.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (3)
  • Cargo.toml
  • README.md
  • hooks/lefthook.yml

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

Comment @coderabbitai help to get the list of available commands.

@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.38%. Comparing base (805e9d3) to head (1bed66b).

Additional details and impacted files
@@           Coverage Diff           @@
##             main       #8   +/-   ##
=======================================
  Coverage   88.38%   88.38%           
=======================================
  Files          24       24           
  Lines        7162     7162           
=======================================
  Hits         6330     6330           
  Misses        832      832           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@HackingGate
HackingGate merged commit 6a40ea3 into main Aug 12, 2026
12 checks passed
@HackingGate
HackingGate deleted the release/v1.1.0 branch August 12, 2026 15:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants