• v0.1.16 e56305692b

    v0.1.16 Stable

    gitea_admin released this 2026-07-06 14:58:26 +00:00 | 212 commits to main since this release

    Changed

    • gitops-flux now follows build→release→deploy (no longer special). The gitops-flux renderer
      (templates/gitops-flux/) restructures to the standard shape, identical to gitops-deploy except the
      deploy engine: the trunk sensor now runs pipeline-staging (validate-flux ▸ noop ▸ pipeline-promote-tag)
      — a SHIPPED clean x.y.z cuts a tag + ff's Forgejo main + Forgejo Release; a plain -dev land only
      validates — and a NEW <project>-deploy sensor fires on main-push → pipeline-deploy-flux
      (anchor=main). The CI filter gains the _devbump/ + release-cadence/ machinery exclusions (the
      taxonomy is now versioned). Pair with pipelines' pipeline-{validate-flux,deploy-flux} template edits
      and each repo's VERSION/CHANGELOG; the PipelineProject versionSource.kind flips nonefile.
      Requires seanfarm/platform-seanfarm CRs on kind: file to actually release (a none CR stays
      validate-only). No new CR schema fields.

    Included changes (v0.1.15 -> v0.1.16)

    • d93ac82b6539 feat(render): gitops-flux follows build->release->deploy (no longer special)
    Downloads