Summary
Note: As the installation process changed we recommend you to take a look at our Installation Guideline if you installed a version of cifuzz < 0.7.0, because we recommend to uninstall previous cifuzz installations before installing v0.7.0 or higher.
- Support
coveragecommand for Bazel projects - New installation directories following established standards
- Improved documentation & sandboxing
How to install
On Linux and macOS, remember to make the downloaded installer executable via chmod +x <installer file>.
You can find more information in our README
What's Changed
- feat: change install directory by @mlsandnerCI in #374
- update docs with new install location by @MarkusZoppelt in #409
- fix: use new cifuzz install path in pipelines by @mlsandnerCI in #408
- bundle: Ensure that the fuzz tests contain no duplicates by @adombeck in #415
- feat(bazel): command completion creates absolute labels by @mlsandnerCI in #413
- build(deps): bump github.com/spf13/viper from 1.13.0 to 1.14.0 by @dependabot in #416
- Remove bazel symlinks by @adombeck in #418
- Improve C++ fuzz test stub and docs by @fmeum in #417
- build(deps): bump github.com/otiai10/copy from 1.7.0 to 1.9.0 by @dependabot in #422
- minijail: Allow read-only access to the whole filesystem by @adombeck in #407
- docs: expand cifuzz installation path section in readme by @mlsandnerCI in #414
- maven & gradle pipeline tests by @florianGla in #426
- installer: Refactor and create symlinks to the cifuzz executable by @adombeck in #423
- pkg/runfiles: Assume cifuzz executable is in $INSTALL_DIR/bin by @adombeck in #424
- installer: Support --install-dir flag again by @adombeck in #425
- cmd/coverage: Support bazel by @adombeck in #403
Full Changelog: v0.6.0...v0.7.0