core:services:kraken:manifest: Fix fetch latest version

[joaomariolago]

Closes #3694

Summary by Sourcery

Bug Fixes:

• Handle extension manifest lookups where the stored version key may be either raw or prefixed with 'v' when fetching the latest version.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adjusts the logic for fetching the latest extension version so it can resolve versions stored with or without a leading 'v' prefix.

File-Level Changes

Change	Details	Files
Update latest extension version lookup to handle version keys with and without a leading 'v'.	Change the return expression in fetch_latest_extension_version to first try the raw version key, then fall back to a 'v'-prefixed key Preserve existing behavior when no versions are available by still returning None in that case	core/services/kraken/manifest/manifest.py

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#3694	Fix the Kraken /extension/{identifier} endpoint so that fetching the latest extension version (stable or not) correctly returns an existing version instead of reporting no stable or no available versions.	✅

---

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

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• Consider normalizing version keys (e.g., stripping or adding the v prefix) at a single point or via a helper method rather than checking both formats inline here, which would make future changes to version formatting easier.
• The nested ternary and chained or in the return statement slightly hurt readability; pulling versions[0] into a named variable and performing the two lookups on separate lines would make the intent clearer.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider normalizing version keys (e.g., stripping or adding the `v` prefix) at a single point or via a helper method rather than checking both formats inline here, which would make future changes to version formatting easier.
- The nested ternary and chained `or` in the return statement slightly hurt readability; pulling `versions[0]` into a named variable and performing the two lookups on separate lines would make the intent clearer.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}