Skip to content

Releases: maruwork/github-optimization

v1.2.16

20 Jun 15:53

Choose a tag to compare

Leads the public landing with the user outcome first: GitHub publication uncertainty becomes an evidence-backed audit report, clear fix targets, and reusable decision records. Also aligns the repository description with that same promise.

v1.2.15

20 Jun 15:27

Choose a tag to compare

Aligns the remaining public-facing support and contributor entry points with the repository landing promise, points users directly to the exact issue templates, and releases the current green default-branch state.

v1.2.14

20 Jun 15:09

Choose a tag to compare

Clarifies the GitHub landing and quickstart path, aligns repo-top metadata, and fixes the Linux bash collector so audit.manifest.yml primary_ci_workflow overrides are respected during hosted CI selection.

v1.2.12

19 Jun 08:19

Choose a tag to compare

GitHub Actions workflows now use actions/checkout v7.0.0, closing the stale Dependabot workflow update. This release keeps the 1.2.11 hosted-hardening changes in place and updates branch/tag/release metadata to the current head.

v1.2.11

19 Jun 08:16

Choose a tag to compare

GitHub hosted hardening now aligns with the shelf's own release expectations: secret scanning, push protection, Dependabot security updates, and master branch protection are enabled. actions/checkout references are updated to v6, stale distribution examples and verdict wording are corrected, and collector regressions were rerun on June 19, 2026.

v1.2.10

19 Jun 07:24

Choose a tag to compare

Branch version metadata now reflects current master. Git Bash hosted metadata and latest CI evidence now match the PowerShell collector's compact schema. PowerShell and Git Bash regulation regressions plus hosted dogfood verification were rerun on June 19, 2026.

v1.2.9

19 Jun 06:09

Choose a tag to compare

  • Stabilize Windows hosted-evidence regression assertions across ABSENT, PASS, and API_BLOCKED issue-template cases.
  • Escape literal gate-text checks correctly so GitHub Actions Windows CI matches local verification.
  • Re-run PowerShell and Git Bash regulation regressions before cutting the release.

v1.2.8

19 Jun 05:50

Choose a tag to compare

  • Fix the Windows hosted-evidence regression test so it no longer depends on JSON property order.
  • Keep release metadata aligned with the current shelf HEAD after the follow-up CI fix.
  • Re-run PowerShell and Git Bash regression coverage for the updated release state.

v1.2.7

19 Jun 05:28

Choose a tag to compare

  • Fix Gitleaks artifact BLOCKED/SKIPPED boundary handling across collectors.
  • Add regression coverage for hosted auth-required evidence classification and fixture setup paths.
  • Re-audit the full shelf and align tracked release metadata to the current HEAD.

v1.2.6

18 Jun 23:19

Choose a tag to compare

v1.2.6

Formal release for the GitHub Optimization audit shelf.

Changes

  • Fixed the Gitleaks evidence artifact boundary so environment execution denials are reported as SKIPPED instead of BLOCKED where direct scoring evidence is required.
  • Added regression coverage for PowerShell and Git Bash collector behavior around Gitleaks access-denied artifacts.
  • Completed strict all-file self-audit for the shelf state at this release.

Verification

  • validate-regulation-index.ps1: PASS
  • check-tracked-files.ps1: PASS
  • check-gitignore-consistency.ps1: PASS
  • run-audit-quickstart.ps1: PASS
  • PowerShell regulation tests: PASS
  • Git Bash regulation tests: PASS
  • GitHub CI / CodeQL: PASS

Notes

This release keeps raw collector evidence separate from scoring evidence. Managed sandbox or Git Bash execution artifacts must not be treated as final G-01 scoring when a direct Gitleaks transcript is required.