Version 3.0.1 file tagging

[mshriver]

Summary by Sourcery

Bump the Ibutsu project and API to version 3.0.1 across backend and frontend metadata files.

Build:

• Update backend project metadata to version 3.0.1.
• Update frontend package metadata to version 3.0.1.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Bumps the Ibutsu project version from 3.0.0 to 3.0.1 consistently across backend OpenAPI spec, backend packaging metadata, and the frontend package manifest.

File-Level Changes

Change	Details	Files
Update API spec version to 3.0.1.	Change OpenAPI spec version from 3.0.0 to 3.0.1 in the root openapi field. Update the documented API version under the info.version field to 3.0.1.	backend/ibutsu_server/openapi/openapi.yaml
Update backend project packaging version to 3.0.1.	Change the Python project version field from 3.0.0 to 3.0.1 in pyproject configuration.	backend/pyproject.toml
Update frontend package version to 3.0.1.	Change the npm package.json version from 3.0.0 to 3.0.1 for the frontend application.	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

• 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 reviewed your changes and they look great!

---

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.}

[Copilot]

Pull request overview

This pull request updates the version number from 3.0.0 to 3.0.1 across the frontend and backend components of the Ibutsu project.

Changes:

• Updated frontend package version to 3.0.1
• Updated backend project version to 3.0.1
• Updated OpenAPI specification and API version to 3.0.1

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
frontend/package.json	Updates the frontend package version from 3.0.0 to 3.0.1
backend/pyproject.toml	Updates the backend project version from 3.0.0 to 3.0.1
backend/ibutsu_server/openapi/openapi.yaml	Updates both the OpenAPI specification version and API version from 3.0.0 to 3.0.1

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The openapi field on line 1 specifies the OpenAPI Specification version being used, not the API version. This should typically remain as 3.0.0 unless you're specifically adopting features or fixes from OpenAPI Specification 3.0.1. The API version should only be updated on line 4 under info.version. Consider reverting line 1 to openapi: 3.0.0 unless there's a specific reason to update the specification version.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.40%. Comparing base (ce6a412) to head (1e49146).
⚠️ Report is 2 commits behind head on main.

❌ Your project status has failed because the head coverage (73.40%) 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     #800   +/-   ##
=======================================
  Coverage   73.40%   73.40%           
=======================================
  Files         154      154           
  Lines        7557     7557           
  Branches      660      660           
=======================================
  Hits         5547     5547           
  Misses       1790     1790           
  Partials      220      220           

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ce6a412...1e49146. 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.