[DIST-PATH-INSTALL] in docs/specs/DISTRIBUTION-SPEC.md tells users to install with:
brew install nimblesite/tap/sharplsp
scoop install nimblesite/sharplsp
Nothing in release.yml pushes to Nimblesite/homebrew-tap or Nimblesite/scoop-bucket, so those commands only work for whatever version someone last updated by hand. docs/plans/DISTRIBUTION-PLAN.md had this ticked as done; it has been corrected to [ ] NOT BUILT.
The blocker is now gone: every release publishes per-platform standalone server archives (sharplsp-<platform>.tar.gz / .zip) plus a SHA256SUMS covering them, which is exactly what a formula and a manifest need.
Remaining work:
[DIST-PATH-INSTALL]indocs/specs/DISTRIBUTION-SPEC.mdtells users to install with:brew install nimblesite/tap/sharplspscoop install nimblesite/sharplspNothing in
release.ymlpushes toNimblesite/homebrew-taporNimblesite/scoop-bucket, so those commands only work for whatever version someone last updated by hand.docs/plans/DISTRIBUTION-PLAN.mdhad this ticked as done; it has been corrected to[ ] NOT BUILT.The blocker is now gone: every release publishes per-platform standalone server archives (
sharplsp-<platform>.tar.gz/.zip) plus aSHA256SUMScovering them, which is exactly what a formula and a manifest need.Remaining work:
Nimblesite/homebrew-tapandNimblesite/scoop-bucketreposreleaseenvironment alongside the existing publish secrets ([DIST-SECRETS])publish-packagesjob torelease.yml, needingrelease, that rewrites the formula/manifest URL + sha256 from the release assets and pushespublish-marketplacehandles--pre-release[DIST-PATH-INSTALL]to drop the "Not yet automated" note once it lands