• New: arch_guard init. Detects the project layout (Clean Architecture, Riverpod, Bloc or feature-first folders), writes a starter arch_guard.yaml, and previews the first scan: files per layer, violations, cycles, and the suggested next step. Options: --preset <name|auto|none>, --dry-run, --force.
• New: Layer presets. preset: clean_architecture | feature_first | bloc | riverpod in the config expands to predefined layers. Entries under layers: override a preset layer key by key (for example only allowed_imports) or add new layers. feature_first discovers features from lib/features/* (or lib/modules/*) on every run, so each feature may import only itself and shared code.
• Improved: Actionable layer violations. Each violation now shows the rule it broke (Rule: `presentation` may only import `core`, `domain`, `presentation`.) and the output ends with how to fix it. SARIF and Markdown reports include the rule too; LayerViolation gains allowedImports, rule and suggestion, and the JSON report includes allowedImports.
• Preset layers that match no files no longer produce "matched no scanned files" warnings.
• Library: ArchGuardConfig.parse() reads configuration from a string; LayerCoverage.layerFileCounts counts files per layer; LayerPresets and LayoutDetector are exported.
• A bad option to arch_guard init now prints the init usage instead of the main one.

v1.4.0

Compare

Choose a tag to compare

• New: Baselines for legacy projects. --update-baseline records today's circular dependencies and layer violations in arch_guard_baseline.json. When that file exists, later runs fail only on new problems: a known cycle may shrink, but one that grows or merges with another counts as new. Fixed entries are reported so the baseline can be tightened. Use --baseline <path> for a different location. Library users get Baseline and BaselineComparison.
• New: SARIF output (-f sarif) writes arch_guard.sarif (SARIF 2.1.0) for GitHub Code Scanning, Azure DevOps and SARIF viewers in IDEs. Results point at the offending import line, use paths relative to the git repository root, and carry baselineState when a baseline is in use.
• New: Markdown summary (-f markdown) writes arch_guard_report.md: new problems first, then a collapsible Mermaid graph of the cycles. Ready for PR comments and CI job summaries.
• New: GitHub Action. uses: creatorpiyush/arch_guard@v1.3.0 downloads the checksum-verified release binary, writes the Markdown summary to the job summary, keeps one up-to-date PR comment, and can upload SARIF to Code Scanning.
• New: pre-commit hook. The repository ships a .pre-commit-hooks.yaml, and the README has recipes for pre-commit, lefthook and plain git hooks.
• New: --version flag and the packageVersion constant.
• Layer violations, graph edges and directives now record the source line (LayerViolation.line, GraphEdge.line, ExtractedDirective.line); the JSON report includes it.
• -f all now also writes the SARIF and Markdown reports.
• Local-only files (plan.md, IDE files, build/) are no longer included in the published package.

v1.3.0

Compare

Choose a tag to compare

• Wider compatibility: minimum Dart SDK lowered from 3.11 to 3.8 (Flutter 3.32+), so projects on older toolchains can add arch_guard as a dev dependency.
• New: Standalone binaries: every GitHub Release now includes prebuilt executables for Linux (x64, arm64), macOS (Apple Silicon) and Windows (x64) plus a SHA256SUMS.txt, so CI pipelines can run arch_guard without installing the Dart SDK.
• CI: Tests run on Linux, macOS and Windows against both the minimum supported SDK (3.8) and the latest stable SDK.
• Fix: Publish workflow ran twice per release: publishing to pub.dev is now triggered by version tags only.
• Removed the Flutter .metadata file from the repository.

v1.2.1

Compare

Choose a tag to compare

• Fix: --scan-dir was ignored whenever workspace discovery was on (the default). A single-package project is no longer treated as a workspace, and in workspace mode the root package honours --scan-dir.
• Fix: Over-eager workspace auto-discovery: without a workspace: list, only packages/ and apps/ are searched, and example/, test/ and tool/ packages are skipped. Previously example/ apps and test fixtures were scanned and could report false cycles. Monorepos with other layouts should declare a workspace: list.
• Fix: Phantom graph nodes: edges are only kept when their target file was actually scanned.
• New: max_scc_size is enforced: any circular-dependency group larger than the limit fails the run (exit code 1), even with --no-fail-on-cycle.
• New: Configuration warnings: unparseable YAML, unknown keys, wrongly typed values, allowed_imports naming unknown layers, layers that match no files, files that belong to no layer, and unreadable source files are now reported on stderr instead of being silently ignored. LayerValidator.coverage(), ArchGuardConfig.warnings and ScanResult.skippedFiles expose the same data to library users.
• New: part directives produce library -> part edges (type part, drawn dotted in DOT/Mermaid/HTML); FileNode.parts lists them.
• Improved: Directive parser now reads the directive section token by token, so // or /* inside URIs or comments, nested block comments, annotations and import-like text inside later string literals no longer cause wrong results.
• Security: HTML report escapes file paths before inserting them into the page and escapes <, > and & in the embedded JSON.
• Rename: DepGraphConfig is now ArchGuardConfig (the old name remains as a deprecated alias). The legacy dep_graph.yaml file and dep_graph_visualizer: pubspec key still work but emit a deprecation warning; the example now uses arch_guard.yaml.
• Tests write CLI output to a temporary directory instead of example/sample_project/build/.

v1.2.0

Compare

Choose a tag to compare

• Fix: Layer validator now works correctly in workspace/monorepo mode (LayerValidator): Layer glob patterns such as lib/domain/** were silently never matching workspace-prefixed file paths (e.g. packages/auth_pkg/lib/domain/entity.dart). The validator now also tests the lib/… suffix of each path, making single-package and workspace arch_guard.yaml configs interchangeable with no user-side changes required.
• Fix: Cross-package edge resolution path separator on Windows (ImportReader.resolveUri): p.normalize(p.join(…)) could produce backslash-separated paths on Windows, causing all resolved edge targets to silently miss the forward-slash-keyed filesMap and disappear from the graph. All three return paths now force / separators.
• Fix: Missing space in workspace summary line (TextReporter): The Workspace Pkgs: line was missing a space before the count, producing misaligned output (e.g. Workspace Pkgs:3 instead of Workspace Pkgs: 3).

v1.1.3

Compare

Choose a tag to compare

• True --offline HTML Support: Inlined Base64-encoded vis-network.min.js (v10.1.0 UMD) asset and system font fallbacks when --offline flag is specified.
• Physics Stabilization Freeze: Added stabilizationIterationsDone event listener to freeze Vis-Network force calculation after stabilization to eliminate CPU background spin.
• Mermaid Exporter Disambiguation: Added shared ID map with numeric suffix disambiguation for colliding file paths (e.g. a-b.dart vs a_b.dart) and quote label sanitization (#quot;).
• Attribution & Notices: Added THIRD_PARTY_NOTICES.md for bundled vis-network Apache-2.0/MIT software licensing.

v1.1.2

Compare

Choose a tag to compare