* chore(main): release 0.30.12
* chore(release): synchronize release metadata
* docs(changelog): describe 0.30.12 for users
Turn the generated entries into the user-facing notes the changelog keeps, with the --scan example and what each fix changes.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
Format the dashboard with Oxfmt and use tsrs for project builds and Oxlint type analysis. Fix the initial typed findings and check formatting and typed lint in CI to keep new changes consistent.
* chore(main): release 0.30.11
* chore(release): synchronize release metadata
* docs(changelog): write the 0.30.11 entry for users
The generated entry listed commit subjects. Describe what changes for the user, and list the two fixes of #945 separately.
---------
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.9
* chore(release): synchronize release metadata
* docs(changelog): describe 0.30.9 for users
The generated entry listed commit subjects. Rewrite it as what changed
for a user, with the symptom each fix removes, and keep the website
copy identical.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* fix(opencode): preserve v2 directory packages
Stage the reviewed issue 913 source for isolated fork validation. Preserve
package directories and manifests without executing managed packages or
installing their dependencies, and include receipt and localized UI fixes.
Reviewed local source: 15ac88e2f266571b8a6dc8d777302db0f4dcae44
Exact source tree: 45ebabfe2b
Static checks and independent inspection completed. Go, integration,
dashboard, rendering, and hosted runtime validation remain pending.
This fork staging commit is not an upstream publication or merge.
* test(opencode): align schema and snapshot assertions
Check the version-aware binding schema and verify native unregister retains the unchanged managed snapshot.
* fix(opencode): resolve Windows npm native launchers
Probe recognized native Opencode executables without invoking a batch shell; exercise the default version probe on hosted Windows.
* test(opencode): normalize Windows fixture line endings
Avoid doubling carriage returns when Git checks out the npm fixture with CRLF.
* fix(opencode): keep an undetected OpenCode version from blocking other agents
Review of the v2 directory package change found that one failed
`opencode --version` probe failed the whole hooks plan, so a machine
without the binary (a second machine sharing the config, CI, a
devcontainer) could no longer sync hooks to any agent, and doctor and
the dashboard preview failed with it.
Hooks:
- A probe that fails or reports an unknown major now skips only the
OpenCode bindings with one warning per target. Outputs already owned
there are parked, so they are neither rewritten nor removed while the
layout is unknown. The probe runs once per plan, list and import.
- A `package` binding on OpenCode v1 is skipped with a warning instead
of failing the plan.
- The v2 dependency warning is reported once, and only when a package
file is written, so a synced hook no longer keeps doctor yellow.
- `hooks import` reports an unreadable file such as a symlink as that
package's problem; other packages and flat files stay importable.
The package validation problem is reported once instead of twice.
- Directories under `plugins/` are listed as unmanaged only on v2.
Plugins:
- The inventory leaves `plugins/skillshare-NAME` registrations to
hooks, so a synced v2 hook is not offered as an importable plugin.
Dashboard: the new warnings are translated in every locale, a
`hook NAME:` prefix no longer defeats translation, the native preview
translates its per-file error, and the YAML editor documents `package`.
Docs: the English pages and the built-in skill describe the behavior
above; the ja, ko, zh-Hans and zh-Hant pages now carry the same
content as the English ones. The runbook drives the CLI with mdproof
assertions instead of prose expectations.
Refs #913.
---------
Co-authored-by: Willie <egg358358@gmail.com>
* chore(main): release 0.30.8
* chore(release): synchronize release metadata
* docs(changelog): rewrite the 0.30.8 entry for users
The generated entry listed commit subjects. Readers need what changed for
them and what to do: the MCP directory reads are a new capability, the
tracked-repository fixes change what uninstall and unlink remove, and the
theme fix needs the matching desktop app update.
---------
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.7
* chore(release): synchronize release metadata
* docs: rewrite the 0.30.7 changelog for users
Release Please lists commit subjects. The entry now says what each
change means for users, with the --respect-accepted example, migration
details for install --json, and credit for the reports and fixes.
---------
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.6
* chore(release): synchronize release metadata
* docs(changelog): write user-facing notes for 0.30.6
The generated entry listed commit subjects only. Describe each change by what users see, add CI examples for check --exit-code, and give a migration note for self-hosted servers, which no longer receive provider tokens after #861.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
Preserve the complete Layout while adding a standalone Mod named skillshare. Generate both packages from one canonical mod and protect custom layouts and usage meters during installation and updates. Keep release versions aligned and route native Herdr instructions separately within existing context budgets.
Release the automatic version-check opt-out with CLI and dashboard controls, unchanged explicit checks and upgrades, and documented global configuration and environment precedence.
Synchronize the manifest, built-in skill, Herdr panel version and both user-facing changelog copies at 0.30.5. Include the reviewed release documentation from main.
* chore(main): release 0.30.4
* chore(release): synchronize release metadata
* docs(changelog): describe 0.30.4 for users
The generated entry listed commit subjects. Rewrite it as what changes for someone using the Herdr panel, the CLI's --json output, plugin updates and audit, with the reporters credited.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
The panel had no version and no way to update: a user had to copy the mod folder again by hand and could not tell when a newer one existed.
The panel now carries version.js, the skillshare release it shipped with, which Release Please rewrites in every release. While shown it asks once an hour where GitHub's "latest release" link lands and offers "Update panel" when that release is newer. It compares against the published release, not main, because the panel parses the CLI's --json output and a panel from main may need an unreleased CLI.
The update clones only the mod's folder at that tag and copies it over the installed one. It first checks the folder holds the running panel's version, keeps the replaced files once in .bak-update-<version>, and holds every machine's lock until the reloaded panel returns it, because Herdr's reload ends every running task.
* chore(main): release 0.30.3
* chore(release): synchronize release metadata
* docs(changelog): describe 0.30.3 for users
The generated entry listed commit subjects; users need to know what changed for them, with an example for the new Hermes target and the audit change that can now block tracked installs.
---------
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.2
* chore(release): synchronize release metadata
* docs(changelog): describe 0.30.2 for users
Replace the generated commit list with user-facing entries for the three
fixes users can notice: the Python docstring audit severity, the dashboard
restart on Homebrew, and the root-scope nested repo check. Dashboard-only
UI polish and the test-only CI fix are left out.
---------
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.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>