v2.2.0

🚀 Engine Upgrade: Support for Zenzic v0.15.0

⚙️ Core Engine Bump

• Zenzic v0.15.0 Support: The underlying engine dependency has been upgraded to fully support the latest Zenzic v0.15.0 features.

✨ New Capabilities

• Native Z603 Detection: CI/CD workflows utilizing this action will now natively detect and flag Z603 DEAD_SUPPRESSION violations out of the box. This ensures that unused or orphaned zenzic:ignore directives are caught in PRs and never merged into your main branch.

🧹 Maintenance

• Updated CHANGELOG.md and isolated legacy release history to maintain clean governance.

v2.1.1

What's Changed

• fix(config): purge legacy i18n configurations and harden release automation by @PythonWoods-Dev in #29

Full Changelog: v2...v2.1.1

v2.1.0 — Zenzic Core v0.14.0

zenzic-action v2.1.0

⬆️ Core Upgrade

This release pins the GitHub Action to Zenzic Core v0.14.0.

What's new in Core v0.14.0

• Z506 MALFORMED_FRONTMATTER: New rule detecting broken frontmatter delimiters.
• Z405 infra exemptions: robots.txt, _redirects, CNAME, sitemap.xml auto-exempt.
• Governance fixes: JSON and SARIF formatters now correctly apply per_file_ignores
  and directory_policies. SARIF results in GitHub Advanced Security are now accurate.
• Breaking: [i18n] config section and Z602 suppressions removed from core.
  Update .zenzic.toml before upgrading.

Usage

- uses: PythonWoods/zenzic-action@v2
  with:
    zenzic-version: "0.14.0"

---

Core release notes: zenzic v0.14.0
Full Changelog: CHANGELOG.md

v2.0.0: SARIF Fix Integration (Core v0.13.1)

Zenzic GitHub Action v2

This release synchronizes the GitHub Action with the Zenzic v0.13.0 core release.

Core Engine Update

This release updates the underlying Zenzic engine default pin to v0.13.1.

Bug Fixes

• SARIF Governance Exclusions: By bumping the core engine to 0.13.1, the Action now correctly respects per_file_ignores and directory_policies when upload-sarif: 'true' is used. This ensures that GitHub Advanced Security Code Scanning only receives active findings and ignores properly managed technical debt.

Usage

Users utilizing the v2 major tag will automatically receive this update:

uses: PythonWoods/zenzic-action@v2
with:
  upload-sarif: 'true'
  strict: 'true'

### 🚀 Highlights
- **Engine Bump:** Updates the internal runtime to Zenzic `v0.13.1`.
- **Improved Action Output:** Adapts to the newly refined Zenzic CLI UX, ensuring `FATAL` and `HALT` codes are bubbled up explicitly in the GitHub Actions runner UI.
- **Strict Configuration Passthrough:** Inherits the active defense TOML validation, ensuring users' misconfigured `.zenzic.toml` paths fail clearly and loudly.

**Full Changelog**: https://github.com/PythonWoods/zenzic-action/compare/v2...v2.0.0

**Full Changelog**: https://github.com/PythonWoods/zenzic-action/compare/v2...v2.0.0

v1.4.0

What's Changed

• chore(deps): Pinned Zenzic Core version to 0.11.0
• fix: Removed obsolete README.it.md requirement from the internal pinning scripts

This release updates the default execution target of the GitHub Action to use the newly released Zenzic Core v0.11.0 engine.

Full Changelog: v1.3.5...v1.4.0

v1

What's Changed

• ci(release): automate GitHub Release on tag push by @PythonWoods-Dev in #5
• Release v1.1.0: Native Telemetry Gate & Core v0.9.0 Alignment by @PythonWoods-Dev in #7
• docs(action): EN/IT readme policy sync by @PythonWoods-Dev in #8
• docs: audit contributing guidance by @PythonWoods-Dev in #9
• release: v1.2.0 by @PythonWoods-Dev in #10

Full Changelog: v1.0.1...v1

What's Changed

• docs(changelog): retroactively deprecate v1.3.0 and older due to config bug by @PythonWoods-Dev in #17

Full Changelog: v1.3.1...v1

What's Changed

• chore(release): bump to v1.3.4 and core 0.10.3) by @PythonWoods-Dev in #20

Full Changelog: v1.3.3...v1

What's Changed

• chore(release): bump version to 1.3.5 by @PythonWoods-Dev in #21

Full Changelog: v1.3.4...v1

What's Changed

• chore(release): v1.4.0 by @PythonWoods-Dev in #22

Full Changelog: v1.3.5...v1

zenzic-action 1.3.5 — Core pin 0.10.4, CI fix & branch protection policy

What's changed

Changed

• Zenzic core pinned to 0.10.4 (x-zenzic-core-pin marker updated in action.yml)

Fixed

• check-core-pin-local CI failure: added fetch-tags: true to the zenzic core checkout step so tag v0.10.4 is visible in shallow clones

Documentation

• Branch protection operational policy documented in CONTRIBUTING.md
• SSH commit signing setup instructions added to CONTRIBUTING.md
• Badge centering fixed in README.md / README.it.md

Full changelog

https://github.com/PythonWoods/zenzic-action/blob/main/CHANGELOG.md

v1.3.4: Enterprise Governance Alignment & Dependency Security

What's Changed

• chore(release): bump to v1.3.4 and core 0.10.3) by @PythonWoods-Dev in #20

Full Changelog: v1.3.3...v1.3.4

v1.3.3

What's Changed

• Release v1.3.3: Pin Zenzic Core to v0.10.2 by @PythonWoods-Dev in #19

Full Changelog: v1.3.2...v1.3.3

v1.3.2

What's New in v1.3.2

This patch release hardens the action's execution environment to remain completely silent and perfectly agnostic across non-Python technology stacks.

Bug Fixes

• Silent Setup-uv: Disabled internal dependency caching in the astral-sh/setup-uv step. Since Zenzic is frequently used as a documentation linter on non-Python projects (e.g., Node.js, Docusaurus), the setup-uv action was previously throwing noisy warnings looking for non-existent pyproject.toml or lock files. The execution is now stealthy and warning-free across all stacks.

Dependency Updates

• Bumped astral-sh/setup-uv from v8.1.0 to v8.2.0
• Bumped actions/checkout from v6.0.2 to v6.0.3

---

Full Changelog: v1.3.1...v1.3.2