0.4.0

⚠️ Breaking Changes
This release includes a database schema change. Action is required if you are updating an existing installation.

Database Schema Update: The primary key for the slack_messages table has been changed from a single column (pr_number) to a composite primary key of pr_number and gh_repository. This change is critical for correctly handling identical PR numbers across different repositories.

Action Required: You must run the latest database migration to update your schema. Please consult the Upgrade Documentation for a detailed upgrade path.

✨ Features and Enhancements
Production-Ready Docker Environment: We've introduced full Docker support for production usage, which will significantly simplify the deployment, installation, and scaling of the PR bot.

See the Production Docker Documentation for setup instructions.

Data Integrity Refactoring: The core SlackMessage entity and related code have been refactored to enforce data integrity using the new composite primary key, guaranteeing that unique messages are tracked per repository.

🐛 Fixes
Multi-Repository Update Fix: Resolved an issue where message updates were incorrect or failed when multiple registered repositories had pull requests with the same number. (Fixes #15: Message is not updated when multiple repositories with the same RP number)

Ignored Draft PR Creation: The bot now correctly ignores events for newly created Draft PRs, preventing the bot from attempting to process a pull request before it's been marked as ready for review.

Full Changelog: 0.3.3...0.4.0