Skip to content

chore(submodule): bump evo-ai-processor-community for OpenRouter fix (EVO-1684)#124

Open
marcelogorutuba wants to merge 9 commits into
developfrom
marcelo/evo-1684-openrouter-prefix
Open

chore(submodule): bump evo-ai-processor-community for OpenRouter fix (EVO-1684)#124
marcelogorutuba wants to merge 9 commits into
developfrom
marcelo/evo-1684-openrouter-prefix

Conversation

@marcelogorutuba

@marcelogorutuba marcelogorutuba commented Jun 22, 2026

Copy link
Copy Markdown
Member

Summary

Validation

  • Smoke manual: agente LLM com chave sk-or-v1-... (provider=openrouter) + modelo openai/gpt-4.1 → resposta normal (antes: AuthenticationError: Incorrect API key).
  • Unit tests do submódulo: 9 passed, 2 skipped (rodam no CI com ADK stack).

Changed Files

  • evo-ai-processor-community (pointer bump)

Linked Issue

  • EVO-1684

Summary by Sourcery

Bug Fixes:

  • Pull in the OpenRouter routing/authentication fix via an evo-ai-processor-community submodule bump.

@sourcery-ai

sourcery-ai Bot commented Jun 22, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the evo-ai-processor-community submodule reference to a newer commit that includes the OpenRouter routing fix via LiteLLM, without changing any first-party source files in this repo.

File-Level Changes

Change Details Files
Update evo-ai-processor-community submodule pointer to include OpenRouter routing fix via LiteLLM.
  • Advance the submodule reference to a commit that fixes OpenRouter routing when using LiteLLM (resolving previous AuthenticationError issues with sk-or-v1 keys).
  • Rely on upstream submodule unit tests (9 passed, 2 skipped) for validation, with no direct code changes in this repository.
evo-ai-processor-community

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@marcelogorutuba marcelogorutuba changed the base branch from main to develop June 22, 2026 14:39
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