Conversation
…enhance scanner with warning handling
…tion checks, and CI integration
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
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.
This pull request introduces a comprehensive release and quality gating workflow, adds supporting documentation and configuration, and improves the development and release process for the project. The most significant changes are the addition of automated scripts and policies for release readiness, quality gates, and documentation synchronization, as well as updates to the project metadata and developer documentation.
Release and Quality Gate Automation:
scripts/release-gate.shto enforce release readiness checks, including code quality, artifact integrity, documentation sync, and approval logging. This script outputs release artifacts and summary files for traceability.scripts/quality-gate.shfor running test and lint checks as part of the quality gate.scripts/publish-check.shto automate formatting, testing, linting, packaging, and (optionally) dry-run publishing..github/workflows/release-gate.ymlto run the release gate in CI for PRs and tags.Configuration and Policy Files:
config/release-policy.tomlto define release policy, artifact requirements, lifecycle states, and audit log paths.config/docs-sync-checklist.mdto specify documentation requirements for releases and enforce docs sync via automation.config/quality-thresholds.tomlto register quality gate metrics and thresholds.Documentation and Developer Guidance:
README.mdwith installation instructions, quality/release gate usage, and new directory structure for config and scripts. [1] [2] [3]CONTRIBUTING.mdto require running release and publish checks for relevant changes and to include new PR guidelines. [1] [2].github/PULL_REQUEST_TEMPLATE.mdrequiring summary, testing, docs impact, and release readiness checklist.Project Metadata:
Cargo.tomlto version 0.2.0 and explicitly declared the binary target. [1] [2]These changes collectively enforce higher release standards, automate critical checks, and improve the onboarding and workflow for contributors.
References:
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15]