Skip to content

Releases: stackitcloud/rag-template

v2.1.0

v2.0.1

16 Jul 11:50
dab9b2d
Compare
Choose a tag to compare

2.0.1 (2025-07-16)

Bug Fixes

  • update log file paths and bump image tags to v2.0.0 (#53) (dab9b2d)

v2.0.0

15 Jul 12:48
accd0a3
Compare
Choose a tag to compare

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!

v1.2.0

23 Jun 11:16
2b0e037
Compare
Choose a tag to compare

1.2.0 (2025-06-23)

Features

  • provide the chat of the rag by MCP (#27) (2b0e037)

v1.1.0

16 Jun 09:20
02036cf
Compare
Choose a tag to compare

1.1.0 (2025-06-16)

Features

  • add Confluence integration with configurable parameters to admin-frontend (#19) (438d10b)
  • add sitemap loader to admin frontend (#21) (02036cf)

v1.0.0

21 Jan 14:17
Compare
Choose a tag to compare

Release Notes – Version 1.0.0

Release Date: 2025-01-21

We are exited to announce the initial release of our project! This first version lays the groundwork for document management, extraction, the rag-backend itself as well as frontend capabilities. Below are the highlights of what’s included, along with known issues and a glimpse of what’s coming next.


What’s New

  • Core Functionality: Introduced basic document management, extraction, rag-backend and frontend features (#3537317)
  • Working Example: Implemented the first running example to demonstrate core capabilities (#f633787)
  • Infrastructure: Added initial infrastructure as a submodule (#d84f750)
  • Dependency Injection (DI): Created a foundational DI overwriting example for the core library (#4f927c7)
  • Project Essentials: Added README.md and .gitignore files (#c289259)

Improvements

  • Code Organization: Established the initial code structure and folder setup (#7f838fe)
  • Project Setup: Performed the initial commit and laid out the project basics (#c289259)

Known Issues

  • Certain edge cases have not yet been thoroughly addressed.

Contributions

Special thanks to everyone who contributed their time and expertise to make this initial release possible.

What’s Next

  • Additional features and enhancements are planned for upcoming releases.
  • We welcome suggestions, issues, and pull requests from the community to help shape future developments.

Happy coding!