Skip to content

Release 3.1.3 - #1126

Open
mshriver wants to merge 1 commit into
ibutsu:mainfrom
mshriver:release
Open

mshriver wants to merge 1 commit into
ibutsu:mainfrom
mshriver:release

Conversation

@mshriver

@mshriver mshriver commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

DB migrations with indicies for runs, results, artifacts

Idempotent re-import of runs, ensuring no duplication of results or artifacts

Explicit float/integer/string handling of metadata and summary data

Better frontend handling of component/env/marker label rendering

Summary by Sourcery

Chores:

  • Bump the backend, frontend, and API versions to 3.1.3.

DB migrations with indicies for runs, results, artifacts

Idempotent re-import of runs, ensuring no duplication of results or
artifacts

Explicit float/integer/string handling of metadata and summary data

Better frontend handling of component/env/marker label rendering

Co-authored-by: Claude <noreply@anthropic.com>
@sourcery-ai

sourcery-ai Bot commented Sep 11, 2026

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

Reviewer's Guide

This PR prepares the 3.1.3 release by synchronizing version metadata across the backend, frontend, and OpenAPI specification. The description also references database indexing, idempotent run re-imports, explicit data-type handling, and frontend label-rendering improvements, but no implementation for those changes is present in the supplied diff.

File-Level Changes

Change Details Files
Bumped the release version consistently across the API specification, backend package metadata, and frontend package metadata.
  • Updated the OpenAPI version to 3.1.3.
  • Updated backend project version to 3.1.3.
  • Updated frontend package version to 3.1.3.
backend/ibutsu_server/openapi/openapi.yaml
backend/pyproject.toml
frontend/package.json

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
Contributor

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 ✨

@codecov

codecov Bot commented Sep 11, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.89%. Comparing base (45a90c8) to head (16dfc0b).
⚠️ Report is 1 commits behind head on main.

❌ Your project check has failed because the head coverage (75.89%) is below the target coverage (85.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1126       +/-   ##
===========================================
+ Coverage   65.03%   75.89%   +10.85%     
===========================================
  Files          91      154       +63     
  Lines        3967     7704     +3737     
  Branches        0      697      +697     
===========================================
+ Hits         2580     5847     +3267     
- Misses       1387     1649      +262     
- Partials        0      208      +208     

see 63 files with indirect coverage changes


Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 45a90c8...16dfc0b. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

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.

1 participant