refactor: update release, build and push github actions #94
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ilding - Added new workflows for creating releases, preparing releases, and publishing libraries on merge. - Implemented logic to derive version from pull request titles and create Git tags/releases accordingly. - Enhanced image building workflows to include digest capturing and improved error handling. - Refactored existing workflows to streamline the process of bumping versions for internal libraries and services. - Introduced scripts for bumping chart versions and updating pyproject dependencies. - Removed obsolete scripts and workflows to clean up the repository.
… management and development workflow - Updated Dockerfiles for services and libs to use Python 3.13 and 3.11.7. - Introduced separate Dockerfile.dev for development environments with optimized caching. - Enhanced dependency installation logic in Dockerfiles to streamline dev and prod setups. - Updated Poetry version to 2.1.3 across all services and libs. - Refined pyproject.toml files to include TestPyPI sources and group dependencies for better management. - Improved logging setup in Dockerfiles for better runtime diagnostics.
- Moved test dependencies to a dedicated group and added pytest and coverage. - Created a separate lint group with flake8 and related plugins. - Added debugpy and rag-core libraries to the dev group. - Updated production dependencies for rag-core libraries to version 2.2.1.
- Updated `pyproject.toml` and `poetry.lock` files to enforce `setuptools` version to be less than 80.9 in multiple services. - Adjusted per-file ignores for linting in `admin-backend` and `document-extractor`. - Streamlined Dockerfiles for `document-extractor`, `rag-backend`, and `mcp-server` to improve build efficiency and user permissions. - Ensured consistent formatting in dependency declarations across services. - Updated versioning for `pdfextractor_server` to 2.2.1. - Added minimal library structures in Dockerfiles to facilitate local package recognition by Poetry.
- Moved `pytest` and `pytest-asyncio` to a new test dependency group in `rag-core-lib`. - Added `coverage` to the test dependencies in `rag-core-lib`. - Created a separate lint dependency group in `rag-core-lib` and included `flake8` and related packages. - Updated markers in `poetry.lock` for better platform compatibility. - Removed `pytest-asyncio` from the `rag-backend` dependencies and adjusted its group to only include `test`.
… prod-local group for development
… Dockerfile cleanup and user permissions; adjust pyproject.toml for local dependencies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request refactors the project's CI/CD pipeline by splitting the release, build, publish, and chart update workflows into dedicated, modular GitHub Actions files. It replaces the previous monolithic
semantic-release.ymlwith a set of specialized workflows, improving maintainability, clarity, and control over the release process. The new workflows automate semantic versioning, internal library publishing, Docker image building, Helm chart publishing, and service lockfile refreshes.Release & Versioning Automation
.github/workflows/prepare-release.ymlto automate semantic version calculation, internal library version bumps, and creation of a "prepare-release" PR after merging tomain..github/workflows/create-release.ymlto create a Git tag and GitHub Release when a "refresh-locks" PR is merged, extracting the version from the PR title.Build & Publish Workflows
.github/workflows/build-images.ymlto build and push Docker images for all services after a release is published, and to collect image digests as artifacts..github/workflows/publish-libs-on-merge.ymlto publish internal libraries to TestPyPI and refresh service lockfiles/pins when a "prepare-release" PR is merged..github/workflows/publish-chart.ymlto bump Helm chart versions and publish them to GHCR after images are built, including a PR to persist version updates.Workflow Cleanups & Refactors
.github/workflows/semantic-release.ymlin favor of the new modular workflows..github/workflows/lint-and-test.ymlto skip jobs for PRs labeled as release-related and switched Docker builds to useDockerfile.devfor development builds. [1] [2]Dependency & Metadata Updates
services/admin-backend/pyproject.tomlto use the correct service name (admin-backend) and set its version to2.2.1.