Skip to content

v0.5.2

Choose a tag to compare

@github-actions github-actions released this 20 Jul 09:38
· 62 commits to main since this release
d7dfd6f

Linmas 0.5.2

Branded Codex plugin experience

Linmas now displays its own logo in the Codex plugin catalog and ships matching icons for all eleven Linmas skills. The public marketplace artifact includes both light and dark plugin branding plus per-skill Codex metadata, so users can identify Linmas consistently in the plugin page and skill list.

Install the stable release from the public marketplace:

codex plugin marketplace add TanKimGwan/linmas --ref v0.5.2
codex plugin add linmas@linmas
codex plugin list

Users already following main can refresh the marketplace and reinstall the plugin:

codex plugin marketplace upgrade linmas
codex plugin add linmas@linmas

After installation or upgrade, restart the Codex desktop/app-server and start a fresh task. An existing task can retain stale MCP child processes or cached plugin metadata from the previous version.

Reproducibility

  • package.json remains the canonical version source for the npm package, MCP server, builder output, and marketplace artifact.
  • npm run sync:codex-marketplace regenerates the tracked plugin and checks every generated file byte-for-byte in tests.
  • Plugin validation covers the manifest, canonical branding assets, all eleven skill icons, and each generated agents/openai.yaml file.
  • Windows CI verifies that generated metadata uses repository-canonical line endings.

Safety boundary

This patch changes presentation and distribution metadata only. Linmas remains defensive-only: offline tools do not transmit data, provider execution still requires confirm_transmission=true, proof creation still requires confirm_write=true, and human review remains mandatory.

Rollback

Remove the plugin with codex plugin remove linmas@linmas. To restore the previous stable release, add the marketplace at --ref v0.5.1, reinstall linmas@linmas, restart the Codex desktop/app-server, and verify discovery from a fresh task. Source rollback should use a Git revert rather than a destructive reset.