2.4 KiB

Raw Blame History

Verstak Official Plugins

The first-party plugin set for Verstak Desktop: Files, Trash, Notes, editor and preview providers, Browser Inbox, Activity, Journal, Todo, Search, Secrets and Templates. Plugin bundles are built into independent directories that the desktop host loads from its plugins/ folder.

Alpha software. Build this repository together with compatible verstak-desktop and verstak-sdk checkouts.

Build

Requirements: Node.js with npm, Go and Python 3. Keep this repository next to verstak-sdk so manifest validation can use the SDK schema.

npm --version
go version
./scripts/check.sh
./scripts/build.sh

The build creates dist/<plugin-id>/ packages. To install them into a sibling desktop checkout:

cd ../verstak-desktop
./scripts/install-dev-plugins.sh

Portable plugin archives

Build target-specific archives on Linux:

sudo apt install gcc-mingw-w64-x86-64
./scripts/package-portable.sh v0.1.0-alpha.1

The command creates release/verstak-official-plugins-linux-amd64-<version>.tar.gz and release/verstak-official-plugins-windows-amd64-<version>.zip, plus SHA256SUMS. Each archive expands directly into the desktop application's plugins/ directory. Frontends and manifests are shared; native Go sidecars are built for the target OS. This is a local package operation and does not create a GitHub Release.

Alpha behaviour

Browser Inbox archives processed captures and can restore them; permanent deletion is a separate action.
Saving a browser link creates a collision-safe .url file. Opening a link is handled by Verstak, so it does not depend on a Linux .url file association.
Activity sessions can be scoped to a durable workspace identity or to an explicit unassigned scope. Journal creation is always a user action.
Todo is optional: Overview uses it only when the Todo capability is present.

Publish a GitHub Release

./scripts/publish-github-release.sh v0.1.0-alpha.1

The publisher requires an authenticated gh CLI and a clean, up-to-date main. It runs the local release command, creates and pushes an annotated tag if necessary, then creates or updates the GitHub Release with the archive and SHA256SUMS. Re-running it for a tag that points at the current commit replaces the release assets.

2.4 KiB Raw Blame History