Releases: kondukto-io/kdt
Releases · kondukto-io/kdt
Release v1.0.22
What's Changed
- Feature #69: Added condition for custom params check and requirement fields by @fleimkeipa in #70
- Feature #1902: Implemented the new disabled scanners feature by @yeyisan in #80
- Feature #2250: Implemented the new Default Team feature by @yeyisan in #87
- Feature #2330: Preset scans support for Checkmarx scans @fleimkeipa in #88
- Bugfix/Update readme with new commands by @ckalpakoglu in #71
Full Changelog: v1.0.21.15...v1.0.22
Release v1.0.21.15
Changes in release
- Fix: Deleting business units from the product while creating a project
Release v1.0.21.14
Changes in release
- You can create team via kdt!
Release v1.0.21.13
Changes in release
- New feature: You can ping kondukto server to control that is running.
kdt ping
- Improvement: Whitespaces will be remove in project name.
Release v1.0.21.12
Changes in release
- Fix sbom upload without project name problem
Release v1.0.21.10
Changes in release
- New command
project
has been released. You can check ALM project availability on kondukto.
Usage example:
kdt project available -a $ALM_TOOL_NAME -r $PROJECT_ID
kdt project available -a gitlab -r 1234567
Exit code : 0 -> Project available on kondukto
Exit code : -1 or 255 -> Project not available on kondukto
Release v1.0.21.9
Changes in release
- Adds a new feature to overwrite the given project name.
--overwrite
: Overwrite the project name, there is no need to add a-
suffix.
Full Changelog: v1.0.21.6...v1.0.21.9
Release v1.0.21.8
Changes in release
- Fixed: Always shown update message even If you already use latest version of kdt.
- Improved:
kdt release
feature is improved.
Release v1.0.21.7
Changes in release
- Improved Security Criteria message. Additionally, you got more information about failed security criteria if you pass
-v
flag.
Release v1.0.21.6
Changes in release
- Versioning is changed to version-commitSha
- CI/CD pipelines are fixed
- kdt will override old scan parameter. It is necessary because before of version v1.0.21.4, a corrupt scan param might be created. With this release, if you trigger a new scan, old scan parameter will be updated.