skillshare v0.29.1 Release Notes

TL;DR

1. New projects are saved in config.yaml again. 0.29.0 kept every new project on the machine that added it; now a project you add reaches every machine that shares your config. Machine-local projects are still there when you ask for them.
2. Switch branch for any git source. The dashboard's Branch picker now works for skills installed from SSH remotes, Gitea and self-hosted servers.

Fixed: new projects are saved in config.yaml again

In 0.29.0, project add, edit and remove, and the dashboard's Projects page, wrote to a machine-local registry. If you share config.yaml between machines, a project added on one of them never appeared on the others. project add and Add project save in config.yaml again.

To keep a project on this machine only:

skillshare project add ~/work/scratch --target claude --machine-local

Or make machine-local the default for new projects, and opt one into config.yaml with --shared:

# config.yaml
projects_storage: machine-local

Move a project between the two:

skillshare project share scratch      # machine-local -> config.yaml
skillshare project localize shop-web  # copy a config.yaml project to this machine

share asks before it replaces different settings that config.yaml already has for the project; --yes skips the question and is required with --json.

Edits and removals stay in the file that holds the project. Removing this machine's copy of a project that config.yaml also declares brings config.yaml's version back; project remove --shared removes it from config.yaml too, for every machine.

In the dashboard, Saved to at the bottom of the Add project dialog picks config.yaml or This machine only, and shows the file each one writes. Machine-local projects are tagged This machine in the list. The target picker filters as you type.

Nothing is migrated. Projects that 0.29.0 saved on one machine stay there; run project share <name> to move one into config.yaml. Projects that 0.29.0 hid on one machine stay hidden until you add them again. (#792, #793)

Fixed: switch branch for any git source

The skill detail page's Branch picker was greyed out ("This source can only use its default branch") for skills installed from an SSH remote such as git@host:org/repo.git, Gitea or a self-hosted HTTPS server. It now lists the branches of any git source, so a skill installed from dev can move back to main. (#787, #790)

Contributors

@chung1912