Skip to content

Release v1.8.4

Latest

Choose a tag to compare

@seakee seakee released this 19 Mar 12:40
· 2 commits to main since this release
3d73c7d

Release Notes v1.8.4

Release Date: March 19, 2026
Previous Version: v1.8.3
Commits: 5 commits since v1.8.3

🎉 Overview

Version 1.8.4 focuses on code generation reliability and PostgreSQL parsing robustness. This release hardens model/repository generation, preserves implicit ID behaviors, and improves identifier safety for generated PostgreSQL models.

🚀 What's New

Codegen Model Safety Hardening

  • Safer Model Generation: Improved guardrails in model generation flow.
  • Stability Improvements: Reduced edge-case failures in generated model output.
  • Test Coverage Updated: Added/updated tests to lock expected behavior.

PostgreSQL Parsing Robustness

  • Identifier Handling Hardened: Improved handling of PostgreSQL identifiers in codegen.
  • Parsing Reliability: Better tolerance for parsing edge cases in schema input.
  • Generation Consistency: More predictable generated model/repository artifacts.

Implicit ID Behavior Fixes

  • Preserve Implicit IDs: Generated models now correctly preserve implicit IDs.
  • Restore ListByArgs Ordering: Fixed implicit ID ordering behavior in ListByArgs.
  • Backward-Friendly Output: Reduces regressions for existing generated code patterns.

🔧 Technical Improvements

Code Generation Core

  • Hardened model.go generation behavior.
  • Hardened repository.go generation behavior.
  • Improved PostgreSQL identifier parsing and safety handling.

Tests

  • Updated model_test.go for implicit ID and generation safety scenarios.
  • Updated repository_test.go for ordering and compatibility checks.

📊 Detailed Statistics

Commit Analysis

  • Total Commits: 5 commits since v1.8.3
  • Feature Commits: 0
  • Fix Commits: 4
  • Docs Commits: 0
  • Merge Commits: 1

Code Changes

  • Files Modified: 4 files
  • Lines Added: 649
  • Lines Removed: 102

Pull Requests

  • PR #11: fix/codegen-model-safety-and-postgres-parsing

🔄 Compatibility Notes

  • No breaking API changes were introduced in this release.
  • The release is backward-compatible for existing runtime behavior.
  • Recommended for users relying on codegen with PostgreSQL schemas.