Skip to content

v1.6.21

Choose a tag to compare

@marmutapp marmutapp released this 19 May 19:34
· 14 commits to main since this release

fix(release): gate npm-release.yml to the private repo so the public-repo orphan push doesn't double-fire

Hotfix for a second failure-mode surfaced by v1.6.19/v1.6.20: the
.github/workflows/ directory rides along in the orphan tree
force-pushed to the public repo by scripts/release.sh public
(it's not in PRIVATE_ONLY_PATHS — intentional, for transparency).
The v* tag push to the public repo then also fires npm-release.yml
there. The public repo has no NPM_TOKEN_OBSERVER secret (and
shouldn't — npm publish belongs to the maintainer side), so the
publish to npm job fails with ENEEDAUTH. The build,
public_release, etc. jobs also wastefully run there, only
"working" because gh release edit + upload --clobber is
idempotent against the same release the private run just created.

What this ship changes:

  • frontend job gains if: github.repository == 'marmutapp/superbased-observer-private'.
    Every other job in the workflow chains on needs: frontend
    transitively (build → publish → release; build → public_release),
    so skipping frontend on the public repo short-circuits the whole
    pipeline cleanly — all jobs report as "Skipped" instead of running
    and failing.
  • No change to behavior on the private repo: every existing condition
    still holds because github.repository == 'marmutapp/superbased-observer-private'
    is true there.

What didn't change:

  • ci.yml (the pre-merge gate) is intentionally left ungated. It
    fires on push: main on the public repo when the orphan commit
    lands, runs the same typecheck + build + test pass against the
    public-tree source, and succeeds. That's a useful free
    cross-check (does the scrubbed public tree still build + pass
    tests?), not a duplicate publish.
  • The orphan tree still includes .github/workflows/ so the
    workflow source remains visible on the public repo. Browsers
    see the same YAML the maintainer ships; CI just doesn't fire.

Downloads

Pre-built binaries for each supported platform are attached below. Linux variants bundle antigravity-bridge.exe next to the observer binary for WSL2 users of the Antigravity adapter.

Platform Asset
Linux x86_64 observer-v1.6.21-linux-x64.tar.gz
Linux arm64 observer-v1.6.21-linux-arm64.tar.gz
macOS x86_64 (Intel) observer-v1.6.21-darwin-x64.tar.gz
macOS arm64 (Apple Silicon) observer-v1.6.21-darwin-arm64.tar.gz
Windows x86_64 observer-v1.6.21-win32-x64.zip

Verify with sha256sum -c SHA256SUMS (or shasum -a 256 -c SHA256SUMS on macOS) from the directory containing the downloads.

Also available via npm: npm install -g @superbased/observer@1.6.21