* feat: add chat_module_mix + chat_ui_mix (testnet-0.2 mix variants)
Add the mix-enabled chat modules as submodules tracking the
feat/logos-testnetv02-mix branch, alongside the stock master-tracked
chat_module/chat_ui. They publish under distinct names (chat_module_mix,
chat_ui_mix per metadata.json), so they don't collide with the non-mix
releases. chat_ui_mix depends on chat_module_mix.
- submodules/logos-chat-module-mix -> logos-co/logos-chat-module@e187825
- submodules/logos-chat-ui-mix -> logos-co/logos-chat-ui@fe86886
- generated per-module release workflows (workflow_dispatch only)
* chore: bump chat_module_mix + chat_ui_mix to librln-linux-fixed tips
chat_module_mix e187825 -> b31880d, chat_ui_mix fe86886 -> 89110b5 — pulls in
the stateless librln hashes for linux + x86_64-darwin (via logos-chat c6a35bf),
so the released modules build on Linux, not just darwin-arm64.
* chore: bump chat_ui_mix to bc06582 (default shardId 0 — fleet receive fix)
* 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>
* Regenerate per-module release workflows with Force build option
The shared workflow machinery now carries the `force_build` toggle (synced
from logos-modules-release-base via the merge of #5), but the 14 existing
per-module `release-<module>.yml` files were generated from the old
template and still used `workflow_dispatch: {}`. Regenerate them from the
updated template so each per-module "Release <module>" run also exposes the
Force build option (replace the current published release when the version
is unchanged).
Mechanically identical to re-running scripts/add-module.sh's template
substitution; the only change per file is the force_build input + its
passthrough to _release-module.yml.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Wrapper delegates to logos-modules-release-action's reusable
unpublish.yml@v1 (remove a whole module or one version; dry_run
first). README notes the action now skips builds whose
<module>-v<version> is already published.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
A forked repo's default GITHUB_TOKEN is read-only, so the release /
rebuild-index jobs fail to create releases or upload assets without an
explicit grant. Declare contents:write on every workflow (and the
per-module template). Documented inline + in the README.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Consumes logos-co/logos-modules-release-action@v1. Mirrors the
logos-modules-v2 production architecture (two-tier reusable
workflows, single-source signing config, rolling index) stripped to
a template:
- logos-repo.json with CHANGE-ME placeholders
- empty .gitmodules + submodules/.gitkeep
- _release-module.yml: signing config in one place (defaults to
unsigned so a fresh fork works immediately; inline/external
documented inline)
- release-all.yml: discovers modules from .gitmodules at run time
(no hand-maintained matrix; clean no-op on an empty fork)
- release-module.yml.template + scripts/add-module.sh: one command
to add a submodule and generate its per-module workflow
- rebuild-index.yml: passthrough to the action's index rebuilder
- README: fork-oriented quick start
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Siddarth Kumar