Skip to content

chore(sync): integrate upstream tailcallhq/forgecode (32 commits)#83

Merged
KooshaPari merged 34 commits into
mainfrom
chore/sync-upstream-2026-07
Jul 3, 2026
Merged

chore(sync): integrate upstream tailcallhq/forgecode (32 commits)#83
KooshaPari merged 34 commits into
mainfrom
chore/sync-upstream-2026-07

Conversation

@KooshaPari

Copy link
Copy Markdown
Owner

Manual upstream sync (merge-upstream auto-sync returned HTTP 409). Merges upstream/main into our fork — our 109 Phenotype commits are the base, 32 upstream commits integrated on top.

Conflicts resolved (3, all generated/docs — no source conflicts)

  • README.md — took upstream's expanded provider list + Community section; our Phenotype credential-security note (~/.forge/.credentials.json 0o600) preserved (it was outside the conflict block).
  • Cargo.lock / package-lock.json — took upstream; regenerated on next build.

All Rust source auto-merged cleanly (anthropic.rs, provider.json, provider_repo.rs, tracker/Cargo.toml). Fork additions (deny.toml, cargo-deny.yml) intact.

⚠ Before merge

Needs cargo build --release + cargo generate-lockfile verification — deferred: host is under memory pressure (swap in HALT). Do not merge until a clean build confirms the lockfile regenerates and workspace compiles.

Stat: 11 files, +1178/-2011 (deletions dominated by package-lock.json churn).

renovate Bot and others added 30 commits June 26, 2026 23:09
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…allhq#3575)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…allhq#3578)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…allhq#3593)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…allhq#3601)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
…allhq#3605)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…allhq#3612)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…allhq#3617)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate Bot and others added 3 commits July 3, 2026 00:41
…callhq#3627)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Merge upstream/main into our fork, integrating upstream changes into our 109
Phenotype-org commits (ours as base). Conflicts resolved:
- README.md: took upstream's expanded provider/community section; our
  credential-security note (0o600 store) preserved outside the block.
- Cargo.lock / package-lock.json: took upstream (regenerated on next build).
All source files auto-merged cleanly. Fork additions (deny.toml, cargo-deny.yml)
intact.

NOTE: needs cargo build + lockfile regen verification before merge (deferred —
host under memory pressure).
@gemini-code-assist

Copy link
Copy Markdown

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Repo admins can enable using credits for code reviews in their settings.

@coderabbitai

coderabbitai Bot commented Jul 3, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 3 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: c7d64858-b909-4cc7-a3d8-edd86077dd15

📥 Commits

Reviewing files that changed from the base of the PR and between 5f6e621 and 4b55afb.

⛔ Files ignored due to path filters (2)
  • Cargo.lock is excluded by !**/*.lock
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (9)
  • Cargo.toml
  • README.md
  • crates/forge_app/src/dto/anthropic/response.rs
  • crates/forge_app/src/transformers/model_specific_reasoning.rs
  • crates/forge_domain/src/provider.rs
  • crates/forge_repo/src/provider/anthropic.rs
  • crates/forge_repo/src/provider/provider.json
  • crates/forge_repo/src/provider/provider_repo.rs
  • crates/forge_tracker/Cargo.toml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/sync-upstream-2026-07
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch chore/sync-upstream-2026-07

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.

@github-actions github-actions Bot added type: chore Routine tasks like conversions, reorganization, and maintenance work. type: provider Updates provider.json configuration. labels Jul 3, 2026
@socket-security

Copy link
Copy Markdown

Dependency limit exceeded — report not shown.

This pull request scan exceeded the 10,000-dependency limit applied to this scan, so the results are incomplete and may be inaccurate. To avoid reporting false positives, Socket has not posted a report.

Upgrade your plan to raise the dependency limit and get complete reports, or view the partial scan in the dashboard.

Socket is always free for open source. If this is a non-commercial open source project, contact us to request a free Team account.

@KooshaPari KooshaPari merged commit c0ad2a3 into main Jul 3, 2026
11 of 20 checks passed
@KooshaPari KooshaPari deleted the chore/sync-upstream-2026-07 branch July 3, 2026 05:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: chore Routine tasks like conversions, reorganization, and maintenance work. type: provider Updates provider.json configuration.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants