v0.4.4

CervoMutants v0.4.4

Changelog

Changed

• The root GitHub Action now declares Marketplace-ready metadata through
  author, branding.icon, and branding.color in action.yml, which keeps
  the action contract unchanged while allowing GitHub Marketplace publication.

Documentation

• Updated the live install and GitHub Action docs to pin v0.4.4 as the
  latest public release and aligned the released external-wave manifest default
  used by the hosted validation workflow.

Verification

• go test ./...
• go run ./cmd/releasehelper verify-compat
• go run ./cmd/releasehelper notes --version v0.4.4 --out .tmp/release-notes-v0.4.4.md

Upgrade Notes

Summary

• v0.4.4 is a patch release focused on the published GitHub Action surface.
• The root action.yml now carries the metadata GitHub expects for GitHub
  Marketplace publication without changing inputs, outputs, or runner-facing
  behavior.
• Installation, release, and hosted-wave alignment docs now point at
  v0.4.4 as the current public release.

Operator Action

• If you pin the GitHub Action by tag, move from @v0.4.3 to @v0.4.4 after
  this release is published.
• No workflow input or artifact-path migration is required for existing action
  consumers.
• If you maintain install or onboarding docs downstream, update any explicit
  v0.4.3 examples to v0.4.4.

Rollback

• If this release causes unexpected GitHub Action behavior, pin back to
  cervantesh/cervo-mutants@v0.4.3.
• If you install via go install, reinstall the prior tag:
  go install github.com/cervantesh/cervo-mutants/cmd/cervomut@v0.4.3.
• If you install from release archives, reinstall the previous v0.4.3
  archive for your target platform.

v0.4.3

CervoMutants v0.4.3

Changelog

Changed

• The hosted external-wave workflow now supports optional manifest-driven
  module prewarm so dependency-heavy targets can run an explicit go mod download step before mutation execution when needed.
• Hosted wave result and aggregate summary helpers are now decoupled from the
  action version under test, so newer workflow metadata can still summarize
  runs that intentionally pin older released action refs such as v0.4.2.

Documentation

• Published dated hosted validation notes and committed summary artifacts for:
  • the Prometheus medium-service prewarm validation wave
  • the v0.4.2 helper-compatibility rerun after helper/action-source
    decoupling

Verification

• go run ./cmd/releasehelper verify-compat
• go run ./cmd/releasehelper notes --version v0.4.3 --out .tmp/release-notes-v0.4.3.md

Upgrade Notes

Summary

• v0.4.3 is a patch release that packages the latest hosted-wave supported
  surface fixes after v0.4.2.
• Hosted external-wave manifests can now opt specific jobs into module prewarm
  before mutation execution.
• The hosted wave workflow no longer couples its summary helpers to the action
  version under test, which keeps newer workflow metadata compatible with older
  pinned action refs.

Operator Action

• If you rely on the first-party GitHub Action and want the newest hosted-wave
  operational behavior, move the tag from @v0.4.2 to @v0.4.3.
• If you maintain your own copy of .github/workflows/external-action-wave.yml
  or its helper flow, re-read the current separation between action-source
  and workflow-source before carrying older snippets forward.
• If you run dependency-heavy hosted-wave targets, decide explicitly whether to
  set prewarm_modules: true in those manifests rather than assuming the
  workflow always prewarms by default.

Rollback

• Reinstall v0.4.2 if this patch causes rollout friction and you need to
  return quickly to the prior public release.
• If rolling back from hosted-wave manifests, also revert any automation or
  documentation that assumes prewarm_modules exists or that helper execution
  is decoupled from the pinned action ref.
• Keep the rollback within the same install family where possible:
  • go install github.com/cervantesh/cervo-mutants/cmd/cervomut@v0.4.2
  • reinstall the v0.4.2 GitHub release archive

v0.4.2

CervoMutants v0.4.2

Changelog

Changed

• Hosted external-wave result and summary generation now run through tested Go
  helpers in cmd/actionhelper instead of large inline workflow scripts.
• The hosted external-wave workflow now runs those helper commands from the
  checked-out source module, fixing the post-#278 working-directory
  regression on GitHub-hosted runners.

Documentation

• Published a dated current-main hosted-wave verification note and committed
  aggregate summary artifact for the post-hardening rerun after the helper-path
  repair.

Verification

• go run ./cmd/releasehelper verify-compat
• go run ./cmd/releasehelper notes --version v0.4.2 --out .tmp/release-notes-v0.4.2.md

Upgrade Notes

Summary

• v0.4.2 is a patch release that carries the latest hosted external-wave
  hardening work into the public release surface.
• Hosted wave result and summary generation now flow through tested Go helpers
  rather than large inline workflow scripts.
• The release also fixes the helper working-directory regression that was
  exposed when that extraction was first revalidated on GitHub-hosted runners.

Operator Action

• If you pin the first-party GitHub Action, move the tag from @v0.4.1 to
  @v0.4.2 so hosted lanes pick up the repaired helper invocation path.
• If you maintain your own hosted external-wave workflow around
  .github/workflows/external-action-wave.yml, re-read the current helper-path
  assumptions before copying older snippets or partial steps.
• If you review hosted-wave evidence, prefer the new dated current-main note
  and committed aggregate summary when checking whether the latest hosted path
  still produces stable denominator health and actionable-yield signal.

Rollback

• Reinstall v0.4.1 if this patch causes rollout friction and you need to
  return quickly to the prior public release.
• If rolling back from hosted-wave workflows, also restore any automation or
  documentation that assumes the repaired helper working-directory behavior.
• Keep the rollback within the same install family where possible:
  • go install github.com/cervantesh/cervo-mutants/cmd/cervomut@v0.4.1
  • reinstall the v0.4.1 GitHub release archive

v0.4.1

CervoMutants v0.4.1

Changelog

Changed

• Hosted adoption-wave summaries now distinguish raw recommendation entries
  from collapsed recommendation review units, and raw governance suggestion
  totals from per-status governance counts, which makes released GitHub Action
  evidence easier to interpret without hiding the raw totals.
• The published first-party GitHub Action now uses actions/setup-go@v6,
  removing the stale Node 20 deprecation path from the released action surface.
• Windows compatibility validation is more deterministic:
  pre-canceled pool commands no longer start real processes, and the serial
  runner budget/quarantine coverage no longer depends on real-clock races.

Documentation

• Published dated follow-up notes for released adoption-wave recommendation
  review units and governance suggestion status counts.

Verification

• go test ./...
• go run ./cmd/releasehelper verify-compat
• go run ./cmd/releasehelper notes --version v0.4.1 --out .tmp/release-notes-v0.4.1.md

Upgrade Notes

Summary

• v0.4.1 is a patch release that tightens the released GitHub Action surface
  and sharpens how released adoption-wave artifacts describe review workload.
• Hosted adoption-wave summaries now preserve review-unit recommendation counts
  and governance suggestion status counts in addition to the existing raw
  totals.
• The release also hardens two Windows-only CI pain points that were still
  showing up as rerun-prone flakes after v0.4.0.

Operator Action

• If you pin the first-party GitHub Action, move the tag from @v0.4.0 to
  @v0.4.1 so the released action picks up the current setup-go@v6 surface
  and the latest hosted-wave/reporting refinements.
• If you use released adoption-wave artifacts to judge rollout quality, start
  reading these fields together instead of overloading the raw totals:
  • recommendation_entries
  • recommendation_review_units
  • collapsed_recommendation_duplicates
  • governance_total_suggestions
  • governance_suggestions_by_status
• If you validate CervoMutants on Windows runners, rerun pressure should be
  lower after this patch, but keep the same bounded-lane discipline and
  version pinning you already use for release adoption.

Rollback

• Reinstall v0.4.0 if the new release causes friction and you need to return
  quickly to the previous public surface.
• If rolling back from hosted-wave or adoption-analysis workflows, also return
  any interpretation docs or automation that assumed the new recommendation
  review-unit or governance-status fields.
• Keep the rollback within the same install family where possible:
  • go install github.com/cervantesh/cervo-mutants/cmd/cervomut@v0.4.0
  • reinstall the v0.4.0 GitHub release archive

v0.4.0

CervoMutants v0.4.0

Changelog

Added

• Semantic triage v1 with pkg/triage, actionable scoring, semantic grouping,
  actionable-only survivor views, and triage-aware report fields.
• GitHub-native review surfaces including SARIF, GitHub summary output, and
  first-party GitHub Action support for the standard CI path.
• Historical dashboards, recommendation surfaces, ownership routing, and
  baseline review lifecycle expansion for more durable survivor governance.
• Pool campaign orchestration, benchmark-corpus support, and committed example
  workspaces for small, medium, and large-repo adoption paths.

Changed

• The public support story now includes an explicit compatibility matrix,
  additive compatibility policy, and daemon/worker narrowing as an
  experimental-only surface until protocol versioning exists.
• Release automation now verifies release notes, archive contents, checksums,
  upgrade handoff, go install, and archive-install report flows before
  publication.
• Public CI and release guidance now reflect the first hardened cross-platform
  validation lane on GitHub Actions.

Documentation

• Added adoption guidance, rollout playbooks, maintainer operations guidance,
  adoption feedback intake, hosted-layer scope notes, and commercialization
  guardrails for the OSS core.
• Published the 24-month roadmap v2 and refreshed the project maturity
  assessment against the current repo-head evidence.

Verification

• go test ./...
• go run ./cmd/releasehelper notes --version v0.4.0 --out .tmp/release-notes-v0.4.0.md
• go run ./cmd/releasehelper verify-compat

Upgrade Notes

Summary

• v0.4.0 is the first release that packages the repository's current
  semantic-triage, GitHub-native review, compatibility-policy, and release
  hardening work into one public version.
• The release expands review surfaces with actionable scoring, semantic
  grouping, GitHub summary output, SARIF, history dashboards, recommendations,
  and first-party GitHub Action support.
• The release also makes support boundaries clearer: daemon/worker remains
  explicitly experimental, while install, upgrade, and report compatibility are
  validated more aggressively before publication.

Operator Action

• If you run CervoMutants in CI, prefer the first-party GitHub Action and
  review docs/github-action.md plus
  docs/go-toolchain-compatibility.md before widening the lane.
• If your workflow reads survivor output or reports, review the new
  actionable-only and semantic-triage surfaces. The raw report model stays
  additive, but teams should re-baseline any local expectations that were based
  only on pre-triage survivor ordering.
• If you previously treated daemon/worker as an implied future distribution
  contract, narrow that expectation now. The public docs treat it as
  experimental until a versioned protocol exists.
• Before promoting this release broadly, run a bounded lane and confirm that
  your install path, report readers, and baseline posture still match the
  documented workflow.

Rollback

• Reinstall v0.3.0 if the new review surfaces, CI integration path, or
  compatibility expectations create rollout friction that needs to be backed
  out quickly.
• If rolling back, also restore the previous baseline or survivor-review
  expectations when they depended on pre-v0.4.0 ranking or governance shape.
• Keep the rollback within the same install family where possible:
  • go install github.com/cervantesh/cervo-mutants/cmd/cervomut@v0.3.0
  • reinstall the v0.3.0 GitHub release archive

v0.3.0

Highlights

• Harden Windows-native mutation execution with safer temp-root handling, conservative worker defaults, and report metadata for runtime warnings (#29, PR #48).
• Add large-repo CI slicing mode with deterministic sharding and per-run file or mutant caps for bounded CI execution (#19, PR #49).
• Close the survivor-ranking manual calibration loop with a documented multi-repo review sample and a safer default: conditionals-boundary now ranks as higher equivalent-risk instead of competing with clearly actionable survivors (#13, PR #50).

Verification

• go test ./...

Docs

• Added docs/evaluations/2026-06-17-survivor-ranking-calibration.md.

v0.2.0

Highlights

• Added first-class resource statuses in reports, including memory_killed, skipped_resource, and pending_budget.
• Added stopped_reason, last_completed_mutant, and per-mutant memory_peak_bytes to report outputs.
• Added structured failure artifacts for run and eval, including failure payloads in mutation-report.json, failure-debug.json, correlation IDs, and panic recovery across CLI and engine entrypoints.

Included issues

• #18 Add first-class timeout and memory statuses to reports
• #22 Convert panics and internal failures into structured results

Verification

• go test ./...

v0.1.0

CervoMutants v0.1.0

Initial GitHub release for CervoMutants.

Highlights

• aligned the repository, module path, and documentation with the CervoMutants project name;
• added Apache License 2.0 for the codebase;
• added NOTICE attribution and TRADEMARKS.md guidance for the project name, logos, and branding;
• published the current CLI/library/reporting baseline from main as the first GitHub release.

Validation

• go test ./...

Included work

• PR #44
• Issues #42 and #43