New Features
- [Config UI] Adds data scope to the connections section: #4760
- [Config UI] Combines data entities and transformation rules into a scope config, simplifying the configuration process: #5159
- [Config UI] Allows users to customize the Grafana URL on the sidebar of the Config UI for a personalized experience: #4121
- [Framework] Enables enrichment to be run independently without executing the entire blueprint, improving flexibility and efficiency: #4866
- [Framework] Supports project, blueprint, and scope deletion for better management of DevLake components: #4864
- [Data Schema] Supports multiple assignees for issues in the issue tracking domain: #4738 (Requires re-running the pipeline for correct data)
- [Data Schema] Adds an "original_status" field to the "pull_requests" table, using "status" to indicate standardized statuses: #4745 (Requires re-running the pipeline for correct data)
- [Data Schema] Provides a "calendar_months" table or view to simplify SQL queries for time-series metrics: #4747
- [Jira] Collects data in the Jira development panel: #4304
- [Zentao] Collects Zentao issue changelogs and issue_repo_commits: #5189 , #5190
- [GitHub] Enhances the capability of Github to allow multiple labels to match a single regular expression: #5079
Bug Fixes
- [Config UI] Fixes the readability and consistency of task names displayed on the status page: #5088
- [Data Schema] Fixes inconsistency in the data transformation logic to the DevLake domain layer, ensuring accurate and reliable data processing: #5193
Breaking Changes
- [Refactor] Renames "ENCODE_KEY" to "ENCRYPTION_SECRET" and makes the .env file readonly and optional: #5235
- [Grafana] Upgrades Grafana to the latest version, providing enhanced features and improvements: #5017 (Please note that the built-in Grafana has been replaced by the official Grafana dependency. Remember to delete the existing Grafana deployment before upgrading to avoid any errors.)
- [Config UI] Combines data entities and transformation rules into a scope config, simplifying the configuration process: #5159
- [Data Schema] Renames the table "finished_commits_diffs" to "_tool_refdiff_finished_commits_diffs": #5193
- [Framework] Enables enrichment to be run independently without executing the entire blueprint, improving flexibility and efficiency: #4866
How to Upgrade
Please follow the steps below to upgrade Apache Incubator DevLake:
Important Note: This upgrade requires manual configuration for the "ENCRYPTION_SECRET" (previously known as "ENCODE_KEY"). You can copy the value of your existing "ENCODE_KEY" and set it as the value for "ENCRYPTION_SECRET".
For Docker Compose and Kubernetes (k8s) Users:
- Update your docker-compose.yml or k8s-deploy.yaml file with the following image tags:
- devlake.docker.scarf.sh/apache/devlake:v0.18.0-beta1
- devlake.docker.scarf.sh/apache/devlake-dashboard:v0.18.0-beta1
- devlake.docker.scarf.sh/apache/devlake-config-ui:v0.18.0-beta1
- Set the value for "ENCRYPTION_SECRET" by copying the value of your existing "ENCODE_KEY". Please refer to the documentation at Docker Compose Setup for detailed instructions based on your installation method.
For Helm Users:
- Follow the instructions provided in the documentation at Helm Setup.
- Ensure that you have set the value for "ENCRYPTION_SECRET" by copying the value of your existing "ENCODE_KEY".
Upgrade Notes:
For detailed upgrade instructions and further information, please refer to the documentation at Upgrade Guide.