Skip to content

Conversation

@evaline-ju
Copy link
Contributor

@evaline-ju evaline-ju commented Jun 9, 2025

Follow-up to #487

Summary by Sourcery

Chores:

  • Bump TrustyAI Guardrails orchestrator version from 0.9.4 to 0.10.0 in component_metadata.yaml

@sourcery-ai
Copy link
Contributor

sourcery-ai bot commented Jun 9, 2025

Reviewer's Guide

Upgrade the TrustyAI Guardrails orchestrator to version 0.10.0 by updating its metadata entry in the component configuration file.

State Diagram for TrustyAI Guardrails Orchestrator Version Update

stateDiagram-v2
    direction LR
    state "Version 0.9.4" as V0_9_4
    state "Version 0.10.0" as V0_10_0

    V0_9_4 --> V0_10_0 : Upgrade of TrustyAI Guardrails Orchestrator in component_metadata.yaml
Loading

File-Level Changes

Change Details Files
Bump orchestrator version in metadata
  • Replace version string 0.9.4 with 0.10.0
config/component_metadata.yaml

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

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

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

Here's what I looked at during the review
  • 🟢 General issues: all looks good
  • 🟢 Security: all looks good
  • 🟢 Testing: all looks good
  • 🟢 Documentation: all looks good

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.

@evaline-ju
Copy link
Contributor Author

evaline-ju commented Jun 9, 2025

Change already included in #490 - closing

edit: never mind, that was on a release branch

@evaline-ju evaline-ju closed this Jun 9, 2025
@evaline-ju evaline-ju reopened this Jun 9, 2025
@ruivieira ruivieira added the kind/enhancement New feature or request label Jun 10, 2025
@openshift-ci
Copy link

openshift-ci bot commented Jun 10, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ruivieira

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ruivieira ruivieira moved this to In Review in TrustyAI planning Jun 10, 2025
@openshift-ci
Copy link

openshift-ci bot commented Jun 12, 2025

New changes are detected. LGTM label has been removed.

@evaline-ju
Copy link
Contributor Author

rebased to hopefully avoid trivy large file failure

@github-actions
Copy link

PR image build and manifest generation completed successfully!

📦 PR image: quay.io/trustyai/trustyai-service-operator-ci:7b320089951ab83a5289cdc07a018dbc609850a9

📦 LMES driver image: quay.io/trustyai/ta-lmes-driver:7b320089951ab83a5289cdc07a018dbc609850a9

📦 LMES job image: quay.io/trustyai/ta-lmes-job:7b320089951ab83a5289cdc07a018dbc609850a9

📦 Guardrails orchestrator image: quay.io/trustyai/ta-guardrails-orchestrator:7b320089951ab83a5289cdc07a018dbc609850a9

🗂️ CI manifests

devFlags:
  manifests:
    - contextDir: config
      sourcePath: ''
      uri: https://api.github.com/repos/trustyai-explainability/trustyai-service-operator-ci/tarball/operator-7b320089951ab83a5289cdc07a018dbc609850a9

@openshift-ci
Copy link

openshift-ci bot commented Jun 12, 2025

@evaline-ju: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/trustyai-service-operator-e2e 7b32008 link true /test trustyai-service-operator-e2e

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind/enhancement New feature or request ok-to-test

Projects

Status: In Review

Development

Successfully merging this pull request may close these issues.

2 participants