diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 96e5e8b..03f1c01 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -20,6 +20,10 @@ jobs: git config user.email "$GITHUB_ACTOR@users.noreply.github.com" - name: Run chart-releaser - uses: helm/chart-releaser-action@v1.1.0 + uses: helm/chart-releaser-action@v1.4.0 + with: + # charts_dir: charts + config: cr.yaml + # charts_repo_url: xxxxxx env: CR_TOKEN: "${{ secrets.TOKEN }}" \ No newline at end of file diff --git a/charts/cdefense/Chart.yaml b/charts/cdefense/Chart.yaml index b3e3282..facce90 100755 --- a/charts/cdefense/Chart.yaml +++ b/charts/cdefense/Chart.yaml @@ -13,9 +13,9 @@ type: application # This is the chart version. This version number should be incremented each time you make changes # to the chart and its templates, including the app version. # Versions are expected to follow Semantic Versioning (https://semver.org/) -version: 0.1.1 +version: 0.1.2 # This is the version number of the application being deployed. This version number should be # incremented each time you make changes to the application. Versions are not expected to # follow Semantic Versioning. They should reflect the version the application is using. # It is recommended to use it with quotes. -appVersion: "0.1.1" +appVersion: "4.5.1" diff --git a/charts/cdefense/values.yaml b/charts/cdefense/values.yaml index 9b01738..41a786a 100644 --- a/charts/cdefense/values.yaml +++ b/charts/cdefense/values.yaml @@ -1,4 +1,4 @@ -version: "release-4.5.0" +version: "release-4.5.1" domain: clouddefenseai.com hostname: console.clouddefenseai.com diff --git a/cr.yaml b/cr.yaml new file mode 100644 index 0000000..d9e869f --- /dev/null +++ b/cr.yaml @@ -0,0 +1,3 @@ +owner: cdefense +# git-base-url: https://api.github.com/ +release-notes-file string: release.md \ No newline at end of file diff --git a/release.md b/release.md new file mode 100644 index 0000000..58223fc --- /dev/null +++ b/release.md @@ -0,0 +1,21 @@ +New Features + +Users now integrate Bitbucket Server and also scan their own repository. +SCA scan result is now showing groups by also showing based on dependency status. +Auto PR version 2 is implemented. User can now see all the issue in a table and can auto fix +Re-scan is implemented, changing anything with the repository user can easily re-scan that application. +Users can download the scan result status in the PDF version. +Application management is now Dynamic, Super Admin can dynamically assign all application with the team +Scan history result will now showing with more specific with the application id +Now Show and Save Sub Repository Items along with their Scan Status +SAST rules Vulnerability is now super dynamic. “App user” can request to “super user” any vulnerability to make it in the allowed list. “Super user” can approve or decline the allowed list. Also can check previously approved or declined allowed lists. + +Resolved Bugs + +Removing GitHub integration from source control is now fixed. +Bitbucket integration is now fixed. +Bitbucket private repository scan now working perfectly with the scan improvements. +SAST rules error has been fixed while clicking in SAST rules +“Recommendation” is now working. After the scan is completed the user can see the vulnerability Fix recommendation in the result. +DAST scan with error log is now fixed and improved with faster scan. +Authentication service for users is improved and fixed.