chore(repo): refresh uv.lock to v0.2.18 (#239)

[w7-mgfcode]

Closes #239.

Routine post-release lockfile sync — uv.lock forecastlabai version field was 0.2.17; pyproject.toml is now 0.2.18 (released in #285). Re-running uv lock updates the single project-version line.

Diff

Single line in uv.lock:

 [[package]]
 name = "forecastlabai"
-version = "0.2.17"
+version = "0.2.18"
 source = { editable = "." }

No dependency resolution change. Resolved 183 packages in 2.12s — same set as before.

Why this recurs

release-please's extra-files config only manages pyproject.toml (not uv.lock), so every release re-introduces the same one-line drift. Long-term fix would be either:

• Add uv.lock to release-please's extra-files with a regex matching the forecastlabai version line, OR
• A CI step that runs uv lock after the release-please commit and pushes if dirty.

Neither is in scope for this PR — closing the chronic gap can be its own follow-up.

Test plan

• Lockfile-only change — ruff / mypy / pyright not affected.
• CI's Test gate re-runs uv sync to validate the lock is consistent.

Summary by Sourcery

Chores:

• Refresh the uv.lock lockfile after the 0.2.18 release to eliminate version drift between the lockfile and project metadata.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ec42c595-7357-4b6c-bad1-7943aaf5ced4

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/refresh-uv-lock-v0-2-18

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the project version entry in uv.lock to match the released 0.2.18 version in pyproject.toml, with no dependency graph or resolution changes.

File-Level Changes

Change	Details	Files
Align the uv.lock project version with the 0.2.18 release without altering dependencies or resolution results.	Update the forecastlabai package version value in the lockfile from 0.2.17 to 0.2.18 Regenerate the lockfile via uv lock to ensure it is consistent with pyproject.toml while preserving the same dependency set	uv.lock

---

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.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	pypi/​numpy@​2.4.1
	pypi/​pandas@​3.0.3
	pypi/​mypy@​1.19.1
	pypi/​pytest@​9.0.2
	pypi/​pydantic-ai@​1.96.0
	pypi/​joblib@​1.5.3
	pypi/​scikit-learn@​1.8.0
	pypi/​openai@​2.36.0
	pypi/​pyright@​1.1.408
	pypi/​sqlalchemy@​2.0.46
	pypi/​xgboost@​3.2.0
	pypi/​uvicorn@​0.40.0
	pypi/​tiktoken@​0.12.0
	pypi/​lightgbm@​4.6.0
	pypi/​python-dotenv@​1.2.1
	pypi/​pydantic@​2.12.5
	pypi/​ruff@​0.14.14
	pypi/​pyyaml@​6.0.3
	pypi/​pydantic-settings@​2.12.0
	pypi/​pytest-cov@​7.0.0
	pypi/​fastapi@​0.128.0
	pypi/​pytest-asyncio@​1.3.0
	pypi/​structlog@​25.5.0
	pypi/​httpx@​0.28.1
	pypi/​pgvector@​0.4.2
	pypi/​pandas-stubs@​2.3.3.260113

View full report

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