Add color background per version type in version-chooser

[patrickelectric]

Summary by Sourcery

Add dynamic background gradients to version cards based on version type, introduce a beta version checker, and adjust card spacing.

Enhancements:

• Apply a linear-gradient background on version cards using CSS variables mapped to stable, beta, and other versions
• Introduce a backgroundColor computed property to classify image tags as stable, beta, or critical for styling
• Add an isBeta utility function to the Kraken Utils module for beta version detection
• Update version card margin classes for consistent spacing

[sourcery-ai[bot]]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Version cards now feature a dynamic gradient background colored by version type (stable, beta, or other) via a new computed property and utility functions, along with a minor spacing adjustment.

Class diagram for updated VersionCard component and Utils functions

classDiagram
    class VersionCard {
      +backgroundColor(): string
      asTimeAgo(value: string)
    }
    class Utils {
      +isStable(version: string): boolean
      +isBeta(version: string): boolean
    }
    VersionCard --> Utils: uses

File-Level Changes

Change	Details	Files
Add gradient background style based on version type	Introduced :style binding to apply a linear-gradient using backgroundColor Defined backgroundColor computed property to return color for stable, beta, or other tags Imported isBeta and isStable utilities for version checks	core/frontend/src/components/version-chooser/VersionCard.vue
Implement isBeta utility function	Added isBeta to detect beta versions by checking tag content	core/frontend/src/components/kraken/Utils.ts
Adjust version card margin spacing	Updated card class from my-4 to my-1 for tighter vertical spacing	core/frontend/src/components/version-chooser/VersionCard.vue

---

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.

[rafaellehmkuhl]

The idea is awesome and will help a lot when picking a version.

It would be nice to try sticking more to the current color palette. Probably @ArturoManzoli or Elisa can help.

[ES-Alexander]

@dgudiel mentioned the appearance of this isn't super consistent with other parts of the interface.

The suggested alternative is to add stability chips (e.g. "stable", "beta", "dev"), like GitHub's version labels: