Skip to content

v0.18.0-beta6

Pre-release
Pre-release
Compare
Choose a tag to compare
@abeizn abeizn released this 18 Aug 09:33
· 1168 commits to main since this release
2865173

Bug Fixes

  • [Config UI] Fixes documentation link returned 404 error: #5766
  • [Config UI] Fixes data scope succeeds but the scope is never listed: #5853
  • [Confid-UI] Fixes wrong connection numbers when a connection has been deleted: #5857
  • [Zentao] Fixes incorrect url and original project field values in devlake zentao data source: #5874
  • [DORA] Fixes a MTTR case summary does not appear: #5887
  • [DORA] Fixes webhook incidents do not appear: #5886
  • [Github] Fixes github plugin reports 404 error when collecting accounts: #5899
  • [Zentao] Fixes error in data collection from zentao, issue with subtask extractStoryRepoCommits: #5904
  • [Framework] Fixes rerun failed with lock table: #5910
  • [Framework] Added timezone usage docs: apache/incubator-devlake-website#628

New Features

  • [Zentao] Adds proxy API for the zentao plugin: #5869

How to Upgrade

Please follow the steps below to upgrade Apache Incubator DevLake:
Important Note: This upgrade requires manual configuration for the "ENCRYPTION_SECRET" (Formerly referred to as 'ENCODE_KEY' in versions preceding v0.18.0). 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:

  1. Update your docker-compose.yml or k8s-deploy.yaml file with the following image tags:
    • devlake.docker.scarf.sh/apache/devlake:v0.18.0-beta6
    • devlake.docker.scarf.sh/apache/devlake-dashboard:v0.18.0-beta6
    • devlake.docker.scarf.sh/apache/devlake-config-ui:v0.18.0-beta6
  2. 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:

  1. Follow the instructions provided in the documentation at Helm Setup.
  2. 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.