Skip to content

Releases: immohitk/mysql-inventory-management

v0.4.3 — Supplier-offer lifecycle and review

Choose a tag to compare

@immohitk immohitk released this 22 Oct 20:57

Highlights

  • Completed the supplier-offer lifecycle workflow.
  • Added supplier-offer creation, retrieval, updates, activation, and deactivation.
  • Strengthened reference validation and offer business rules.
  • Added supplier-offer review workflow and review persistence.
  • Hardened database migration and test-safety protections.
  • Documented the supplier-offer service contract and project security requirements.

Validation

  • Full test suite: 169 passed, 43 subtests passed.
  • Focused supplier-offer tests: 72 passed, 28 subtests passed.
  • Supplier-offer lifecycle integration tests: 3 passed against a disposable test database.

Database Safety

Tests must use an explicitly configured disposable test database. The protected inventory_db must not be used for integration-test writes.

Release Status

This release packages the supplier-offer lifecycle and review milestone, with supporting documentation and test coverage.

v0.4.2 — Data Migration

Choose a tag to compare

@immohitk immohitk released this 14 Oct 22:04

Highlights

  • Added guarded development-database reset tooling with explicit target confirmation.
  • Made migration and demo-seeding tools configurable through environment settings.
  • Added migration-history tracking and automatic skipping of already-applied migrations.
  • Added explicit database-target verification to protect the existing inventory_db.
  • Documented migration failure handling, recovery procedures, and the fresh development-database workflow.

Validation

  • All 4 existing SQL migrations applied successfully to the isolated development database.
  • A repeat migration run correctly skipped previously applied migrations.
  • A migration failure recovery drill verified failure reporting, absence of a migration-history record for the failed migration, and the possibility of partial MySQL DDL execution.
  • Full automated test suite: 63 passed.

Database Safety

The existing inventory_db remains protected. Migration and reset workflows are restricted to explicitly named development/test databases.

Next Milestones

  • v0.4.3 — Supplier Offer service
  • v0.4.4 — Package and unit logic
  • v0.4.5 — Purchase refactor

v0.4.0 - Purchasing & Stock-In

Choose a tag to compare

@immohitk immohitk released this 08 Oct 15:35

Purchasing & Stock-In

Implemented the complete purchasing and stock-in workflow.

Included

  • Purchase data access layer
  • Purchase service
  • Purchase item management
  • Supplier selection and locking
  • Purchase validation
  • Stock-in inventory logic
  • Transaction management with commit/rollback
  • Purchase history
  • Purchase details view
  • Automatic product stock refresh after purchase
  • Delete selected purchase item
  • Reset purchase workflow
  • Purchase/stock consistency validation

QA

  • Successful purchase workflow
  • Stock increase verification
  • Validation/error handling
  • Supplier locking
  • Purchase reset/delete behavior
  • Transaction rollback verification
  • Purchase-to-stock consistency
  • Python module compilation

Git

Release tag: v0.4.0

v0.3.0 - Core CRUD Milestone

Choose a tag to compare

@immohitk immohitk released this 07 Oct 17:03

What's Included

  • MySQL database connection layer
  • Category CRUD service
  • Product CRUD service
  • Supplier CRUD service
  • Input validation and duplicate protection
  • Foreign-key deletion protection
  • Product relationship validation
  • Basic Tkinter/ttk CRUD GUI
  • Category, Product, and Supplier management screens
  • Manual CRUD QA
  • Project documentation updates

Milestone

This release completes the Core CRUD milestone for the MySQL Inventory Management System.

The project now has a working database layer, core CRUD services, and a basic desktop GUI.

v0.1.0 🏗️ The Foundation

Choose a tag to compare

@immohitk immohitk released this 01 Oct 17:53

The first release of MySQL Inventory Management establishes the project's complete foundation and relational database layer.

Included

  • Project structure and Python environment
  • Project requirements and scope
  • Database architecture documentation
  • MySQL relational schema
  • 7 core database tables
  • Primary and foreign keys
  • Unique and CHECK constraints
  • Referential integrity rules
  • Database indexes
  • Fictional demo/seed data
  • Basic Python application entry point
  • Environment-based configuration template
  • Initial project documentation

Database

The foundation includes:

  • 4 categories
  • 3 suppliers
  • 8 products
  • Purchase and sales transaction structures
  • Product/category/supplier relationships

Verification

The release was verified with:

  • Python environment check
  • pytest discovery
  • Application entry-point check
  • MySQL schema verification
  • Foreign-key verification
  • Constraint verification
  • Index verification
  • Demo-data verification

Next

The next release, v0.2.0, will introduce the core CRUD functionality.