daniel/furtka-apps
1
1
Fork 0
Code Issues Pull requests Projects Releases 7 Packages Wiki Activity Actions
furtka-apps/CHANGELOG.md
Daniel Maksymilian Syrnicki a2e47c2c0c
All checks were successful
CI / validate (push) Successful in 11s
Details
CI / shellcheck (push) Successful in 20s
Details
Release / release (push) Successful in 13s
Details
chore: release 26.9-alpha 
Catalog 26.9-alpha cuts the IT-Tools addition from b2b4793 into a
tagged release so boxes pick it up via on-box sync.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-21 11:18:14 +02:00

2.4 KiB
Raw Blame History

Changelog

All notable changes to the Furtka apps catalog will be documented here. Format: Keep a Changelog. Versioning: CalVer (YY.N) — same scheme as the core Furtka repo.

Unreleased

26.9-alpha - 2026-04-21

Added

  • IT-Tools (v1.0.0, image corentinth/it-tools:latest). A browser toolbox: password/UUID/QR generators, hash and HMAC, Base64 / URL / JWT decoders, JSON/YAML/SQL formatters, regex tester, cron parser, subnet calculator, and the usual long tail. Runs fully client-side — no state, no volumes, no settings. Serves on port 8080.

26.8-alpha - 2026-04-21

Changed

  • fileshare bumped to v0.1.2: adds open_url (smb://{host}/files) so the core UI can render an Open button that deep-links to the share.
  • Uptime Kuma bumped to v1.0.1: adds open_url (http://{host}:3001/) for the same UI Open button. No image or compose changes.

26.7-alpha - 2026-04-20

Added

  • Uptime Kuma (v1.0.0, image louislam/uptime-kuma:1). Self-hosted status monitor — pings hosts, checks HTTPS endpoints, watches Docker containers, and screams on Telegram/webhook when something breaks. No manifest settings: the admin account is created on the first browser visit to port 3001. Persists history + config via one namespaced volume furtka_uptime-kuma_data.

26.6-alpha - 2026-04-20

Added

  • Initial catalog release. Carries one app: fileshare (v0.1.1, SMB share over dperson/samba). Copied from the daniel/furtka seed so boxes on 26.6 see the same fileshare bits whether they pull the catalog or fall back to the bundled seed.
  • Release pipeline + CI parity with the core repo: scripts/build-catalog-tarball.sh, scripts/publish-catalog-release.sh, scripts/validate-catalog.py (CI guardrail — loads every manifest via the vendored furtka.manifest.load_manifest + cross-checks compose volume references).