Skip to content

v2.0.0

Compare
Choose a tag to compare
@github-actions github-actions released this 15 Jul 12:48
· 26 commits to main since this release
accd0a3

2.0.0 (2025-07-15)

Release Date: July 15, 2025
Compare: [v1.2.0…v2.0.0](v1.2.0...v2.0.0)


⚠ BREAKING CHANGES

  • Monorepo Migration (#50)
    Consolidated all sub‑repositories into a unified monorepo structure.


🚀 Overview

This major release merges our fragmented micro‑repo setup into a single, cohesive monorepo. All services, shared libraries, and infrastructure components now coexist in one repository—preserving full commit history from the original archives (rag-core-library and rag-infrastructure).


🔑 Key Highlights

  • Monorepo Structure

    • /services/ – all backend and frontend services
    • /libs/ – shared utility and domain libraries
    • /infrastructure/ – Terraform, Kubernetes manifests, deployment scripts
  • Preserved History

    • All commits from the archived rag-core-library and rag-infrastructure repos remain intact.
  • Enhanced Tooling

    • Refactored CI/CD pipelines for monorepo workflows
    • Consolidated development tools (code generators, linters, formatters) at the repo root

📊 Stats

  • Files Changed: 607
  • Lines Added: 55,900+
  • Lines Removed: 10,212

🛠️ Benefits

  • Simplified Dependency Management – Single source of truth for dependency versions.
  • Better Code Sharing – Libraries are first‑class modules referenced across services.
  • Unified Workflows – One CI/CD pipeline, consistent linting, testing, and release processes.
  • Improved Developer Experience – Clone once to work on any component, with consistent tooling and scripts.

⚠️ Breaking Change Details

Because this is a major structural overhaul, please note:

  1. Adjusted Import Paths
    Update any scripts or references to point to /services/, /libs/, or /infrastructure/ instead of old repo URLs.
  2. CI/CD Configurations
    External repo workflows have been deprecated. Migrate to the new definitions in .github/workflows/.

Thank you to everyone who contributed to issue [#50](#50) and to all the maintainers who tested the migration. Here’s to a more maintainable and streamlined development experience ahead!