Skip to content

v0.4.3

Choose a tag to compare

@github-actions github-actions released this 20 Jun 01:16
edf0681

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