Skip to content

v1.1.0

Choose a tag to compare

View all tags
@canaryGrapher canaryGrapher released this 24 Aug 18:54
· 5 commits to main since this release
v1.1.0
9ee9cbc

Postggresively v1.1.0

August 25, 2026

A focused release on product analytics, in-console bug reporting, and painless upgrades for self-hosted installs—plus the public marketing site.

What's New

In-app Updates

Keep official installs current without leaving the console.

  • Update checks: The console compares your build version to the latest GitHub Release (cached) and surfaces a dismissible banner when a newer tag is available.
  • Help → Updates: See current vs latest, release notes, and apply or copy upgrade commands.
  • PM2 auto-update: Download the matching platform archive, replace bin/ and web/, rebuild the UI, and restart PM2 (step-up confirmation required).
  • Docker Compose path: Pull/recreate published images when Docker is available to the agent; otherwise show exact docker compose pull && up -d commands.
  • Install awareness: Release bundles and Compose set PG_INSTALL_KIND / AGENT_INSTALL_KIND so the console knows how you deployed.

Bug Reporting

  • Help → Report a bug: File a GitHub Issue on workvar/postgressively directly from the signed-in console.
  • Title + description form with automatic version, path, and user-agent diagnostics (no secrets).
  • Official builds bake a GH_BUG_TOKEN at release time; self-built binaries show a clear unavailable message instead of failing silently.
  • Rate-limited per user to reduce spam.

Privacy & Telemetry

  • Account → Privacy & telemetry: Opt in/out of anonymous product analytics (GA4 Measurement Protocol from the backend) and UI analytics (Microsoft Clarity in the browser).
  • Credentials are baked into official binaries/images at build time—operators do not configure GA secrets in .env.
  • Sensitive UI fields (connection strings, SQL, row data) are masked from Clarity.

Marketing Site

  • Standalone marketing/ site for landing, download, and setup guidance (not shipped inside PM2/Docker console bundles).
  • Public download flows against GitHub Releases, plus GA/Clarity/Vercel analytics when configured for that site.

Getting Started

New installs

Upgrading from v1.0.0

PM2 bundle (recommended path in v1.1.0)

  1. Open Help → Updates and use Update now, or download the v1.1.0 archive for your platform.
  2. If updating manually: stop services, replace bin/ and web/, keep config.json / data/ / backups/, run npm run setup, then npm run restart.

Docker Compose

export POSTGGRESSIVELY_VERSION=v1.1.0
docker compose pull
docker compose up -d

(Or use Help → Updates when auto-update is enabled.)

From source
Pull v1.1.0, rebuild agent/backend/web, and restart your process manager.

Known Issues/Limitations

Updates

  • Source/dev builds do not offer auto-update (no release version / install kind).
  • Docker auto-update needs a Docker CLI reachable by the agent and typically a docker.sock mount; default Compose stays notify + commands only.
  • Git/deploy.sh installs are not auto-updated in this release.

Bug reporting

  • Requires an official build with GH_BUG_TOKEN and Issues write access to the upstream repo.
  • No screenshot/attachment upload in v1.1.0.

Telemetry

  • Self-built binaries ship with analytics inert unless you bake credentials yourself.
  • Clarity loads only when a project id is present in the web build.

Carried forward from v1.0.0

  • Single console account; session JWTs are not immediately revocable on password change.
  • Row editing, create/drop database, and agent service control remain PostgreSQL-oriented.
  • Rotating PG_SECRET_KEY invalidates saved connections.

Requirements

Same as v1.0.0: Node.js 18+, Go 1.21+, PostgreSQL 12+, HTTPS (or localhost) recommended for passkeys.

Reporting Issues

Use Help → Report a bug in the console, or open an issue on GitHub with deployment method, versions, repro steps, and logs.

Thank you for using Postggresively!

Full Changelog: v1.0.0...v1.1.0

Assets 9
Loading