Skip to content

v0.4.2

Choose a tag to compare

@dkrayieigh dkrayieigh released this 16 Jun 08:24
· 262 commits to master since this release

Albion Logistics ERP v0.4.2

Stable compatibility release.

Versioning Note

This release resets the public version number from the previous internal 4.1.2 line to 0.4.2.

The project is still pre-1.0 because future migrations are not complete yet, including stable item IDs, qtyByLocation, formal event payloads, and versioned backup schema.

Regression Baseline

  • 41 tests
  • 41 pass
  • 0 fail
  • 0 TODO
  • Test command: npm test

Highlights

  • Stabilized crafted item sale flow.
  • Crafted item sale now reliably closes the modal and shows success feedback even if dashboard refresh fails.
  • Crafted item sale success message now shows:
    • Total sale price
    • Unit sale price
    • Estimated gross profit
    • Unknown cost basis warning when applicable
  • Blocked crafting when required material cost basis is missing.
  • Protected backup import from invalid data overwriting existing localStorage.
  • Preserved legacy backup compatibility.
  • Added regression protection for core cost, ledger safety, backup safety, and crafted item sale behavior.

Current Compatibility Guarantees

  • Existing legacy 賣成品 transactions remain supported.
  • Existing qtyByCity data remains supported.
  • Existing Chinese item keys remain supported.
  • Existing readable JSON and legacy JSON-string backups remain supported.
  • No localStorage schema migration is performed in this release.
  • No SELL_ITEM event migration is performed in this release.

Known Limitations

  • SELL_ITEM remains a future event model.
  • Crafted item sale writes legacy 賣成品 transactions.
  • Profit is currently shown as UI feedback only and is not stored as a separate ledger field.
  • qtyByCity has not yet migrated to qtyByLocation.
  • Chinese item keys have not yet migrated to stable item IDs.
  • Backup schema is not yet formally versioned.
  • Some manual correction flows remain legacy-compatible behavior and should be used carefully.

Recommended Before Use

Export a readable JSON backup before using this release with important data.