Simplify and enhance CI workflows and code quality checks #31
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Setup a release workflow triggered by tag pushes and manual dispatch. Includes validation, testing, SBOM generation, and automated deployment to Maven Central and GitHub Releases.
…nd updating dependencies for SBOM generation.
…configuration Set up QA profiles with support for JaCoCo, SpotBugs, Checkstyle, OWASP Dependency Check, and CycloneDX. Configure plugins for code quality, security analysis, and SBOM generation and update project properties for build consistency.
- Add failsafe report paths for better test coverage in JUnit report step. - Configure `NVD_API_KEY` for OWASP Dependency Check via workflow secrets. - Adjust dependency-check data cache location and keys for improved clarity. - Include JSON format in dependency-check report uploads for extended analysis. - Update plugin configuration in `pom.xml` to support NVD API key and custom data directory.
… signing, and vulnerability disclosure policies
Set up a `dependency-review.yml` workflow triggered on pull requests to `main` and `develop` branches. Configure fail-on-severity, license restrictions, and PR comment summaries to enhance dependency analysis and reporting.
Set up a `codeql.yml` GitHub Actions workflow to perform scheduled and event-driven security analysis for Java/Kotlin code using extended and quality queries.
Set up `dependency-check-suppressions.xml` to manage false positives and non-applicable vulnerabilities. Includes guidelines for suppression review and maintenance.
Set up `.well-known/security.txt` following RFC 9116 to provide security contact details, disclosure policy, and acknowledgment information.
Set up `checkstyle.xml` with Google Java Style as a base and project-specific rules, including file length, line length, naming conventions, import rules, whitespace, braces, and annotations.
Set up `KEYS` file with the project's PGP public key to enable verification of signed release artifacts.
…style rules - Add PGP key ID, fingerprint, and reference to `KEYS` file in SECURITY.md for artifact verification. - Configure indentation rules in Checkstyle for consistent 4-space formatting.
- Introduced `AetherDataFixerTest`, `DataFixerRuntimeFactoryTest`, and `DiagnosticRuleWrapperTest` to validate schema updates, data fixer creation, and diagnostic rule behaviors. - Covers edge cases, null handling, combinator methods, and nested structures for robust coverage.
…-checking logic across multiple classes
…c analysis. Introduce YAML null sentinel handling with utility methods `wrap` and `unwrap` for consistent null representation across SnakeYamlOps.
… behavior, update dependency management, and adjust formatting rules in `checkstyle.xml`.
…defensive copying in `RecordingContext`. Remove unused `dataDirectory` from `pom.xml`.
… modules and increase `LineLength` check limit from 250 to 300 in `checkstyle.xml`.
…onsistency in analysis
Splatcrafter
added
documentation
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
Dependency ReviewThe following issues were found:
License Issuespom.xml
OpenSSF ScorecardScorecard details
Scanned Files
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request introduces several enhancements focused on CI workflows, code quality checks, and static analysis. These updates include:
installwithqaprofile) to align with QA consistency.LineLengthcheck limit.RecordingContext).Checklist