Resolves #33
User perspective
No changes for users of ecformat (only changes in the development process of the project)
Developer perspective
- cargo-deny is now executed differently. The detection of security issues is reported in the CI but does not lead to failings of the following CI jobs. Furthermore, the pre-commit hook does not report security issues anymore. These avoid sudden fails due to new security issues in the database.
- All jobs, which has not a fixed image from an action, now use a image with a fixed (Ubuntu) version. This should avoid problems, like the one fixed with
448e8b550a, in the future. - All linters are executed in the CI, if the
lint.yamlhas changed. This makes sure that they are executed if the config is e.g., the image or linter versions are updated.
Resolves #33
### User perspective
No changes for users of ecformat (only changes in the development process of the project)
### Developer perspective
- cargo-deny is now executed differently. The detection of security issues is reported in the CI but does not lead to failings of the following CI jobs. Furthermore, the pre-commit hook does not report security issues anymore. These avoid sudden fails due to new security issues in the database.
- All jobs, which has not a fixed image from an action, now use a image with a fixed (Ubuntu) version. This should avoid problems, like the one fixed with 448e8b550a0eb64c748215044f85a7505f9d27e1, in the future.
- All linters are executed in the CI, if the `lint.yaml` has changed. This makes sure that they are executed if the config is e.g., the image or linter versions are updated.