chore(main): release 0.2.0

[w7-mgfcode]

Release 0.2.0

Features

• registry: Implement model registry for run tracking and deployments (feat(registry): implement model registry for run tracking and deployments #36)
  • ORM models for ModelRun (JSONB columns) and DeploymentAlias with state machine validation
  • LocalFSProvider for artifact storage with SHA-256 integrity verification
  • 10 API endpoints for runs CRUD, aliases management, artifact verification, and run comparison
  • Comprehensive test suite (103 unit + 24 integration tests)

Bug Fixes

• Add date range filter to SalesDaily cleanup in ingest tests
• Enforce artifact_hash presence before verification in registry routes
• Compute SHA256 from saved file instead of source in storage
• Fix override_get_db to mirror production transaction semantics
• Update database port to 5433 in config and .env.example

Documentation

• Add PHASE documentation for phases 4 (Forecasting), 5 (Backtesting), and 6 (Model Registry)
• Fix markdownlint MD040/MD060 issues in docs

---

This PR bumps the version to 0.2.0 and updates the CHANGELOG.

🤖 Generated with Claude Code

Summary by Sourcery

Prepare the 0.2.0 release by updating the changelog and project version.

New Features:

• Document the addition of a model registry for run tracking and deployments in the changelog.

Bug Fixes:

• Record recent registry, storage, database transaction, and config fixes in the changelog.

Documentation:

• Capture new PHASE documentation and markdownlint improvements in the changelog.

Chores:

• Bump the package version from 0.1.8 to 0.2.0 for the new release.

Summary by CodeRabbit

• New Features

  • Registry model with ORM models and storage provider
  • 10 new API endpoints
  • Expanded test suite

• Bug Fixes

  • Date range filtering
  • Artifact hash validation improvements
  • SHA256 usage enhancements
  • Database transaction semantics alignment
  • Port and configuration updates

• Documentation

  • PHASE coverage notes
  • Markdown formatting corrections

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[sourcery-ai]

Reviewer's Guide

Release bump to 0.2.0: updates project version and changelog to document the new model registry feature set, bug fixes, and documentation improvements.

File-Level Changes

Change	Details	Files
Document 0.2.0 release contents in the changelog.	Add 0.2.0 section with model registry feature details. List associated bug fixes around artifact verification, SHA-256 computation, DB overrides, and DB port config. Record new documentation work on forecasting, backtesting, and model registry phases.	CHANGELOG.md
Bump the package version to 0.2.0 for the new release.	Update the project version field from 0.1.8 to 0.2.0. Align release manifest metadata (if present) with the new version tag.	pyproject.toml .release-please-manifest.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.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request bumps the project version from 0.1.8 to 0.2.0 across release and configuration files, accompanied by a comprehensive CHANGELOG entry documenting new features, bug fixes, and documentation improvements for the release.

Changes

Cohort / File(s)	Summary
Version Manifest Updates .release-please-manifest.json, pyproject.toml	Version bumped from 0.1.8 to 0.2.0 in both files to align with the new release.
Release Documentation CHANGELOG.md	New 0.2.0 section added detailing features (registry model with ORM, storage provider, 10 API endpoints, test suite), bug fixes (date range filtering, artifact hash validation, SHA256 usage, DB transaction semantics, configuration updates), and documentation improvements (PHASE coverage, markdownlint fixes).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 Hip hop, the version hops!
From 0.1.8 up to 0.2.0,
New features bloom, the registry grows,
Bugs are fixed where the flow goes,
Changelog tells the tale so true,
Onwards now, there's much to do! 🚀

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore(main): release 0.2.0' accurately describes the primary change—a version bump and release preparation. It uses a standard commit convention and clearly communicates the main purpose of the PR.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release/v0.2.0

---

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]

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