v0.1.1

LibreCosta Uptime v0.1.1

Security maintenance release for the v0.1 series.

Security and build updates

• Rebuild the five platform distribution archives with the patched Go 1.26.10 toolchain.
• Pin the Docker build stage to golang:1.26.10-bookworm while retaining the existing non-root Distroless runtime.
• Require patched Go releases in CI (Go 1.26.10+ and 1.27.3+) and have the distribution and release workflows select the module's recommended toolchain.

The minimum supported Go language/module version remains 1.26.0. No third-party dependencies are upgraded in this release.

Compatibility

This release changes no Uptime features, CLI commands, HTTP endpoints, YAML configuration, persistent database format or Redis key layout. Existing v0.1.0 deployments do not require a data migration.

Upgrade

Download the v0.1.1 archive for your OS/architecture from GitHub Releases, verify it using the accompanying SHA256SUMS, and replace the executable while the service is stopped. Keep the existing YAML configuration and persistent data.

For Docker deployments, upgrade to ghcr.io/librecosta/uptime:v0.1.1. Preserve the existing configuration mount and persistent data volume; follow the Docker deployment guide.

As with v0.1.0, stop the service before bbolt file backup or offline service management. See the README for platform archives, setup and operational limits.

Licensed under MIT.

v0.1.0

LibreCosta Uptime v0.1.0

The first stable release of LibreCosta Uptime provides self-hosted HTTP/HTTPS
monitoring in a single binary, configured with YAML. Local bbolt persistence is
the default, so no external database is required.

Highlights

• HTTP/HTTPS probes with configurable intervals, timeouts, headers and expected
  status codes, powered by Fiber Contrib Uptime.
• A status dashboard and JSON API with daily history, configurable retention and
  timezone, plus public liveness and readiness endpoints.
• Optional Redis storage, native TLS and single-user Basic Auth using bcrypt hashes.
• CLI configuration validation, service listing, Archive v1 JSON history export,
  and explicit removal of retired services.
• Non-root Docker deployment and a systemd example with persistent storage and
  graceful shutdown.

Install

Download a precompiled archive and SHA256SUMS from
the v0.1.0 release.
Verify the checksum before extracting. The archives include the binary, example
YAML, README, license and dashboard preview; no Go installation is needed.

Platform	Architectures	Archive
Linux	amd64, arm64	.tar.gz
macOS (darwin)	amd64 (Intel), arm64 (Apple Silicon)	.tar.gz
Windows	amd64	.zip

Follow the Quick Start
for Linux/macOS and Windows PowerShell commands. For containers, use
ghcr.io/librecosta/uptime:v0.1.0 (Linux amd64/arm64) with the
Docker guide.
Linux hosts can also use the systemd guide.
Installing via go install github.com/librecosta/uptime/cmd/uptime@v0.1.0 requires Go 1.26+.

Usage limits

• The default listener is 127.0.0.1:18580. Remote access requires native TLS or
  a trusted TLS reverse proxy; Basic Auth alone does not encrypt credentials.
• Stop serve before bbolt backups or service management. One process owns the
  database file at a time; preserve it and your configuration during upgrades.
• Endpoint IDs identify persisted history. Removing an ID from YAML does not
  delete its data. Explicit removal is permanent, with no confirmation prompt
  or automatic export.
• Coordinate all Redis writers before deletion. Shared Redis does not coordinate
  probes, and exports are not transactional snapshots across queries.
• JSON exports are not database backups and cannot be imported. Switching
  storage backends does not migrate history.

Licensed under MIT.