Dario LipicarandClaude Opus 4.8 4f5c91b4f4 Add "Force build" option to the release workflows (#5) ...

"Release all modules" and each per-module "Release <module>" workflow now
take a `force_build` toggle on the Run-workflow form (off by default).
When on, it replaces the current published release even if the version is
unchanged — e.g. the submodule pointer moved while metadata.json#version
stayed the same.

The toggle threads down the existing wrapper chain to the action's
`skip_if_published` input (inverted), so signing config still lives in one
place:

  release-all.yml / release-<module>.yml  --force_build-->
    _release-module.yml  --skip_if_published: !force_build-->
      logos-modules-release-action/release.yml@v1

- _release-module.yml: new `force_build` input -> skip_if_published
- release-all.yml: dispatch input, passed through the matrix fan-out
- release-module.yml.template: dispatch input (so generated per-module
  workflows get it too)
- catalog.sh: matching `--force` flag for `release` / `release-all`
- README: document the toggle

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-22 11:39:07 -03:00

..

_release-module.yml

Add "Force build" option to the release workflows (#5)

2026-06-22 11:39:07 -03:00

rebuild-index.yml

Add permissions: contents: write so forks work out of the box

2026-05-19 14:41:32 -03:00

release-all.yml

Add "Force build" option to the release workflows (#5)

2026-06-22 11:39:07 -03:00

release-module.yml.template

Add "Force build" option to the release workflows (#5)

2026-06-22 11:39:07 -03:00

unpublish.yml

Add unpublish.yml wrapper + document skip-if-published

2026-05-19 15:25:41 -03:00