Skip to content

Omarchy Config Sync v1.3.0

Choose a tag to compare

View all tags
@gladimdim gladimdim released this 25 Sep 16:13
· 4 commits to main since this release
v1.3.0
88c23b3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Git-installed plugins sync as a registry, not as copied files.

  • plugins.json replaces copied plugin code. A plugin folder with a .git checkout is never copied in either direction, so Apply cannot downgrade it or leave omarchy plugin update refusing to fast-forward. Publish records id, version, commit, and source URL instead (credentials stripped from the URL) (#18).
  • Changes tab acts through Omarchy's own installer. Install for a listed plugin that is missing runs omarchy plugin add <source> in a floating terminal, so you see Omarchy's warning and confirm there. Update runs omarchy plugin update <id>, which pulls the plugin's upstream, not the repo.
  • Outgoing rows for the registry. This machine being ahead, or a listed plugin you uninstalled, shows as an outgoing row (unticked by default).
  • Existing copies stop applying. A repo that already holds files under plugins/<id>/ for a git plugin no longer applies them; publishing that plugin's list entry removes the copy from the repo. Plugins without .git (your own, or a clone of a built-in) keep syncing file by file.

Validation: Python test suite (173 passed) and omarchy plugin validate passed.

Assets 2
Loading