* chore(main): release 0.30.1
* chore(release): synchronize release metadata
* docs(changelog): describe 0.30.1 for users
The generated entry listed the Release-As commit as a change and used
commit subjects. Replace it with what users see: the Hubs refresh button
and the parallel plugin update check.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* chore(main): release 0.30.0
* chore(release): synchronize release metadata
* docs(changelog): describe 0.30.0 for users
The generated entry listed commit subjects. Users need the migration step for the new host rule and what each fix changes for them.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* chore(main): release 0.29.2
* chore(release): synchronize release metadata
* docs(changelog): write user-facing notes for 0.29.2
The generated entry listed commit subjects, including a docs-only
commit, without saying what users can now do or what the audit fix
prevents.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* chore(main): release 0.29.1
* chore(release): synchronize release metadata
* docs(changelog): describe 0.29.1 for users
The generated entry only listed commit subjects; spell out what changed for people who share config.yaml, how to keep a project machine-local, and the branch picker fix.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: sim <sim@example.invalid>
* chore(main): release 0.29.0
* chore(release): synchronize release metadata
* docs(changelog): describe 0.29.0 for users
The generated entry listed PR titles. It now says what each change
does for a user, with examples, folds the #785 follow-up into the
unreleased --min-severity feature it fixed, and credits the
contributors. Both changelog copies match.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: sim <sim@example.invalid>
Co-authored-by: Willie <egg358358@gmail.com>
Two causes kept turning main red without any code change:
- docker-sandbox-offline failed when proxy.golang.org dropped a module
download mid-stream during the image build. The sandbox Dockerfile now
retries `go mod download` up to three times.
- Hosted macOS arm64 runners are often short, and the required
integration-test (macos-latest) job then fails with "The job was not
acquired by Runner of type hosted", which blocks merges. A workflow_run
follow-up re-runs such a job once, on the first attempt of a run from this
repository. It uses the single-job re-run endpoint because the job ends as
cancelled, and the docs do not say whether re-running failed jobs covers
that. Jobs that failed for other reasons are left alone.
Hosted macOS arm64 runners often fail to pick up the job ("The job was not
acquired by Runner of type hosted even after multiple attempts"), so the Nix
run turned red on most pushes while the Linux flake check passed. Go code on
macOS is already covered by the required integration-test (macos-latest); the
darwin package build mainly guards the flake and vendorHash, which only change
with flake.nix, flake.lock, nix/, go.mod or go.sum. Run it for those paths and
on manual dispatch.
* chore(main): release 0.28.4
* chore(release): synchronize release metadata
* chore(release): write user-facing notes for 0.28.4
The generated entry listed commit subjects, including the release
request, the withdrawn release commit and fixes to the Herdr panel that
was never released before. Readers need what changed for them: the Nix
flake, Nix-aware upgrades, the new panel and the agent source fix.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
The 0.28.4 Release PR (#767) merged, but GitHub's incident kept its
search index from listing the merged PR, so no tag or draft was made.
0.28.4 should now also ship #778, which the merged release commit
cannot include. Restoring the 0.28.3 manifest and changelog lets
Release Please open a fresh 0.28.4 Release PR over the full range.
Release-As: 0.28.4
* chore(main): release 0.28.4
* chore(release): write user-facing notes for 0.28.4
The generated entry listed commit subjects, including the release
request and fixes to the Herdr panel that was never released before.
Readers need what changed for them: the Nix flake, Nix-aware upgrades,
and the new panel. Also syncs the skill version and website changelog,
which the Release Please run skipped after GitHub rejected its push.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
Herdr users run several agents side by side and had to leave it to see
which skills need an update or a sync. The panel brings that view, plus
install, update, uninstall, audit hand-off and source repository sync,
into a Herdr layout node so it survives space switches.
Install audits its own shallow clone first, because install --json names
a blocked skill without its findings; a block shows them before anything
is written. Pull conflicts show both versions side by side, and
.metadata.json merges per entry with the same rule as MergeMetadata so
installs from both machines are kept.
model.js has no Herdr imports, so make test-herdr covers it in make check
and CI. Docs gain a learn/with-herdr page with translations and a README
highlight, and the context router loads herdr/AGENTS.md with frontend.
* feat: add Nix flake and stop self-upgrade of Nix-store installs
Add flake.nix with packages, overlays.default, checks and a formatter,
building nix/package.nix with the unit tests in the Nix sandbox. The
version comes from the Release Please manifest, so releases need no Nix
edit. A Nix workflow runs `nix flake check` on non-docs changes.
`skillshare upgrade` now detects binaries under /nix/store/ and prints
`nix profile upgrade skillshare` instead of replacing a read-only store
path; update notices and doctor suggest the same command.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(upgrade): give Nix installs the right update path everywhere
The first flake commit sent every /nix/store binary to `nix profile
upgrade`, failed a plain `skillshare upgrade` with exit 1 even when the
CLI was current, and left the dashboard with a generic 500.
- Tell `nix profile` installs (the profile manifest lists the store path)
from NixOS, Home Manager and overlay installs, which are told to update
their configuration and rebuild. Detection lives in one helper shared by
the update notice, doctor, upgrade and the dashboard.
- `upgrade` on Nix reports "already up to date" or prints the hint and
exits 0; the built-in skill still updates.
- The dashboard runs the upgrade so the skill updates, then answers
409 `upgrade.nix` with the command when a newer CLI waits on Nix. The
UI shows localized text for it in all 11 locales.
- Installs skip the unit tests; the flake's checks enable them. postPatch
lowers only the go directive's patch version and fails evaluation with
a clear message when go.mod needs a newer Go minor. CI also builds the
package on macOS.
- Docs, translations, the built-in skill reference and the release topic
describe the new behaviour.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Windows temporary paths can use a spelling that differs from the path returned by filepath.EvalSymlinks. Canonicalize test roots before relativizing callback paths and restore internal/sourcewalk to the windows-test allow-list.
* chore(main): release 0.28.0
* chore(release): synchronize release metadata
* docs(changelog): rewrite 0.28.0 entry for users
The generated entry listed raw commit subjects, including a docs commit
and an internal skill fix that users never see. Describe each feature
and fix by its visible behavior, with examples and credits, and keep
the website copy in sync.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
Feature PRs have arrived with a self-ticked "maintainer approved" box on
issues the maintainer never answered, and with large AI-generated diffs
the author could not stand behind. Make approval a label only the
maintainer can add, and state what an AI-assisted contribution owes
reviewers: an author who has read the diff, answers reviews personally,
does not split changes to dodge the size guideline, and makes only
checkable claims.
Add global project list, show, add, edit, sync and remove so setup scripts
can register repositories without editing YAML or opening the dashboard.
Keep dry runs read-only and report completed work when a target fails.
Reuse the shared project service and sync runners. Include command docs,
translations, completions and regression coverage. Quote overlap hints for
their shell and log partial project syncs consistently with ordinary sync.
SKILLSHARE_CONFIG can select a global config in a directory named
skillshare or .skillshare. Treating it as a project config puts logs and
a .gitignore beside the shared config and labels global logs as project logs.
Exclude selected and read-only global config paths from project routing.
Share the check with the log command so readers and writers agree.
Run the legacy config regression explicitly in Windows CI so it is exercised
without enabling unrelated tests that still need Windows fixes.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* chore(main): release 0.26.4
* chore(release): synchronize release metadata
* docs(changelog): describe 0.26.4 for users
The generated entry lists commit subjects; users need to know what each change does for them and how to use it.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* chore(main): release 0.26.1
* chore(release): synchronize release metadata
* docs(changelog): describe 0.26.1 for users
Replace the generated entry with user-facing notes so the release body
explains what changed in the dashboard and in the tracking guidance.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
Correct Unix-only resolution expectations on Windows and pin terminal and renderer state so the package is deterministic. Add theme to the Windows test job to catch future platform regressions. Related to #344.
* chore(main): release 0.25.13
* chore(release): synchronize release metadata
* docs(changelog): write the 0.25.13 entry for users
Replace the generated notes with user-facing descriptions and an example
config for mcp serve skill editing, and drop the Release-As request line.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
The windows-test job lists only the packages verified to pass on Windows, so
that the job is green on arrival. internal/memory never reached that list: it
is absent from #344's set of failing packages, and no commit ever added it,
which leaves its 36 tests unrun on the platform whose binaries are published.
Cross-compiled the package's test binary for windows/amd64 and ran it on a
real Windows host: 36 top-level tests passed, 0 failed, exit code 0. The
symlink call sites in store_test.go skip or drop their subcases when the
privilege is missing, so a runner without Developer Mode cannot fail on them.
* chore(main): release 0.25.12
* chore(release): synchronize release metadata
* docs(changelog): write user-facing 0.25.12 notes
The generated entry listed commit subjects only. Describe each fix by what a
user sees: the token in ps, unchanged skills reinstalled by update --all, the
silent fetch failure, missed updates behind symlinks, and the dashboard
breaking after upgrade, with examples and issue references.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* chore(main): release 0.25.11
* chore(release): synchronize release metadata
* chore(release): write user-facing notes for 0.25.11
Replace the generated commit list with notes that explain what users
see: the MCP pin and tool-change checks with examples, the backup
cleanup fix, and the list detail panel's Targets row. The internal
skills code-review change is left out because it does not reach users.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* chore(main): release 0.25.10
* chore(release): synchronize release metadata
* docs(changelog): describe 0.25.10 for users
Replace the generated commit list with what changed on the dashboard: Open folder on the MCP page and a project's Agent files on its MCP tab.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* chore(main): release 0.25.9
* chore(release): synchronize release metadata
* docs(release): write user-facing notes for 0.25.9
Replace the generated commit list with notes that describe each change
from the user's side, with examples, matching the recent entries.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* chore(main): release 0.25.8
* chore(release): synchronize release metadata
* docs(changelog): rewrite 0.25.8 notes for users
The generated entry listed the raw commit subject. Describe the macOS OMP install fix with the message users saw and the command that now works.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* chore(main): release 0.25.7
* chore(release): synchronize release metadata
* docs(changelog): rewrite 0.25.7 notes for users
The generated entry listed raw commit subjects. Describe the OMP version fix and the plugin update dialog fix in the changelog's usual style, with the error users saw and what changed.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* chore(main): release 0.25.4
* chore(release): synchronize release metadata
* docs(changelog): restore the curated 0.25.4 entry and add #511, #513, #515
Release Please regenerated the entry when #513 landed on main. Restore
the user-facing version and describe the three fixes merged since: the
skills source named like a tool folder (#511, via #514), the hidden
agents source folder (#515) and moved installed skills (#513).
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
These packages were left out of the windows-test job because of failures
that came from test assumptions (POSIX paths, permission bits, HOME,
bash shims posing as git), not product behavior. Fix them and add the
packages to the list so they stay green.
Two failures were real product bugs:
- swapStagedIntoSource named its backup like the temp that
sourcefs.MoveIn creates beside it. On a coarse clock (Windows) both
names matched, the failed move removed the temp and with it the
backup, and the old skill was lost.
- MetadataStore.GetByPath looked up OS-native paths in slash-form keys,
so `update --group` missed nested skills on Windows.
The test sandbox now also sets USERPROFILE, which os.UserHomeDir reads
on Windows; tests were reading the real profile.
Refs #344
Ten tests assumed POSIX behaviour:
- Five asserted os.ModeSymlink, but Windows links with a junction;
check utils.IsLinkMode instead.
- Two used `/abs/...` as an absolute path, which has no volume on
Windows; give the fixtures one.
- Windows has no permission bits to preserve, so the 0600 check is
skipped there.
- Reading a file as a directory reports not-exist on Windows, which
prune ignores, so that prune-error test is skipped there.
- A single-file extension relies on the shebang and the executable bit,
so ListExtensions finds only directory extensions on Windows, as the
extras docs describe.
Add ./internal/sync and ./internal/trash to the windows-test package
list so they stay green.
Refs #344