Bump litellm from 1.57.8 to 1.74.15.post1#171
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [litellm](https://github.com/BerriAI/litellm) from 1.57.8 to 1.74.15.post1. - [Release notes](https://github.com/BerriAI/litellm/releases) - [Commits](https://github.com/BerriAI/litellm/commits) --- updated-dependencies: - dependency-name: litellm dependency-version: 1.74.15.post1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Owner
|
Thanks for submitting this PR! I had to take a step back from Archon so I wasn't able to get to this, but for good reason! The massive overhaul for Archon turning it into the operating system for AI coding assistants is coming soon! I'll be closing this PR due to this, but if you want to implement something similar for the new Archon please feel free to make another PR! |
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
POWERFULMOVES
added a commit
to POWERFULMOVES/PMOVES-Archon
that referenced
this pull request
Feb 12, 2026
…extraction-for-test_integration.py Normalize PMOVES.yt ingest metadata extraction
coleam00
pushed a commit
that referenced
this pull request
Apr 7, 2026
…) (#173) * Investigate issue #171: RouterContext not populated for non-slash commands * Fix: RouterContext not populated for non-slash commands on GitHub (#171) The RouterContext was not being populated for non-slash commands on GitHub because the orchestrator only extracted context from the issueContext parameter (used by slash commands). For non-slash commands, the GitHub adapter embeds context in the message parameter, which was being ignored. Changes: - Extract RouterContext from message when issueContext is undefined - Prioritize issueContext over message when both are present (backward compatibility) - Add contextSource field to debug logs to distinguish extraction source - Add tests for non-slash command context extraction - Add test to verify issueContext takes precedence over message Fixes #171 * Archive investigation for issue #171 * Update investigation for issue #171: Regression in workflowType handling * Fix: Only set isPullRequest when GitHub context markers present The previous fix for issue #171 (commit 87b2ef3) introduced a regression where isPullRequest was always set to true/false, preventing workflowType from isolationHints from being used as a fallback type indicator. Changes: - Only set isPullRequest when GitHub context markers are detected - Updated tests to include required GitHub context markers - Allows workflowType to display correctly when no GitHub context Fixes regression in workflowType handling from commit 87b2ef3 * Archive investigation update for issue #171 * fix: reduce log noise by gating context extraction behind GitHub markers - Only extract title/labels when GitHub context markers are present - Non-GitHub platforms (Telegram/Slack/Discord) no longer trigger noisy logs - Removed "No labels found" log since many issues legitimately lack labels - Kept title extraction warning when GitHub context IS present but format fails - Maintains backward compatibility: issueContext always used for slash commands
Tyone88
pushed a commit
to Tyone88/Archon
that referenced
this pull request
Apr 16, 2026
…leam00#171) (coleam00#173) * Investigate issue coleam00#171: RouterContext not populated for non-slash commands * Fix: RouterContext not populated for non-slash commands on GitHub (coleam00#171) The RouterContext was not being populated for non-slash commands on GitHub because the orchestrator only extracted context from the issueContext parameter (used by slash commands). For non-slash commands, the GitHub adapter embeds context in the message parameter, which was being ignored. Changes: - Extract RouterContext from message when issueContext is undefined - Prioritize issueContext over message when both are present (backward compatibility) - Add contextSource field to debug logs to distinguish extraction source - Add tests for non-slash command context extraction - Add test to verify issueContext takes precedence over message Fixes coleam00#171 * Archive investigation for issue coleam00#171 * Update investigation for issue coleam00#171: Regression in workflowType handling * Fix: Only set isPullRequest when GitHub context markers present The previous fix for issue coleam00#171 (commit 87b2ef3) introduced a regression where isPullRequest was always set to true/false, preventing workflowType from isolationHints from being used as a fallback type indicator. Changes: - Only set isPullRequest when GitHub context markers are detected - Updated tests to include required GitHub context markers - Allows workflowType to display correctly when no GitHub context Fixes regression in workflowType handling from commit 87b2ef3 * Archive investigation update for issue coleam00#171 * fix: reduce log noise by gating context extraction behind GitHub markers - Only extract title/labels when GitHub context markers are present - Non-GitHub platforms (Telegram/Slack/Discord) no longer trigger noisy logs - Removed "No labels found" log since many issues legitimately lack labels - Kept title extraction warning when GitHub context IS present but format fails - Maintains backward compatibility: issueContext always used for slash commands
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps litellm from 1.57.8 to 1.74.15.post1.
Release notes
Sourced from litellm's releases.
Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)