chore: move to Silo-Community and add catalog release workflow - #1
Merged
Merged
Conversation
Relocates the module to github.com/Silo-Community/silo-plugin-tailscale after the repository transfer and prepares it for the approved community plugin catalog. - Fill in the manifest presentation URLs the catalog requires (homepage, source, support, changelog, publisher). - Add a Release workflow that runs `make dist`, publishes the reproducible ZIP archives plus the raw `plugin-<os>-<arch>` binaries and `checksums.txt` the Silo installer expects, and dispatches `plugin_release_published` to Silo-Community/silo-plugins. - Add CODEOWNERS, SECURITY.md, and a community maintenance section in the README. Verified with `make check` and `make dist VERSION=0.1.3`. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
9 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The repository moved from
ironicbadger/silo-plugin-tailscaletoSilo-Communityso it can be listed in the approved community plugin catalog. The module path, manifest, and release process still pointed at the old location, and there was no workflow that publishes assets in the shape the Silo installer and catalog updater expect.Changes
github.com/Silo-Community/silo-plugin-tailscale(go.mod, imports,scripts/dist.py).manifest.jsongains the presentation URLs the catalog validator requires: homepage, source, support, changelog, and publisher. Plugin ID and publisher name are unchanged..github/workflows/release.yml. It runsmake distso the reproducible ZIP archives are still the source of truth, then also publishes the rawplugin-<os>-<arch>binaries and achecksums.txtcovering both. The catalog updater keys on theplugin-prefix and the server installer verifies raw binaries againstchecksums.txt, so the ZIPs alone are not installable from the catalog. The final step dispatchesplugin_release_publishedtoSilo-Community/silo-plugins.CODEOWNERS(@ironicbadger and @Quick104),SECURITY.mdpointing at private vulnerability reporting, and a community maintenance section in the README. These are approval policy requirements.Validation
make checkandmake dist VERSION=0.1.3pass locally.plugin-linux-amd64from the ZIP and confirmed its SHA-256 matches thechecksumin the embeddedmanifest.json.Verify and package) is green on this branch.BuildPackageFromReleaseaccepts this manifest with the new asset layout, tested againstsilo-pluginson SDK v0.16.1.Follow-up
The catalog tooling needs an SDK bump before it recognises
network_access_provider.v1; that is a separate PR onSilo-Community/silo-plugins. Approval and registry entry follow after both merge.Related issue: Silo-Server/silo-server#1001
AI disclosure
Written with Claude Code using
claude-fable-5-1. Reviewed and validated by @Quick104.🤖 Generated with Claude Code