From 369418467408c3552e694db5d36008bd70e3793e Mon Sep 17 00:00:00 2001 From: Dillard Blom Date: Sun, 1 Nov 2026 12:03:19 +0100 Subject: [PATCH] Version 1.0.1: changelog, README status and roadmap --- CHANGELOG.md | 8 +++++++- PLAN.md | 2 +- README.md | 11 +---------- appinfo/info.xml | 8 ++++---- 4 files changed, 13 insertions(+), 16 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index e6d2d42..f162337 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -11,7 +11,10 @@ Each heading starts with that ``, once: the app store shows a release t whose heading starts with its `x.y.z` and ignores anything after it, so `## [1.0.0-rc.6]` would be shown under 1.0.0. The git tag of a release candidate goes after the date. -## [Unreleased] +## [1.0.1] - 2026-11-01 + +Fixes for what was reported after 1.0.0 (#22, #24) and small improvements. Nothing changes in +your backups or settings. ### Added - `occ backup:user:list [location] [user]` shows the user exports on a location, with the manifest @@ -53,6 +56,8 @@ shown under 1.0.0. The git tag of a release candidate goes after the date. - A restore that was stopped (a crash, a timeout, a restart) left its half-written temporary file (`.ngb-restore-`) next to the file it was restoring, and a `files:scan` then showed it in Files. A restore now removes such leftovers in each folder it writes to. +- The app store showed the notes of every release candidate under 1.0.0, because their headings + started with "1.0.0-rc". Each heading now starts with the app version of that release. ## [1.0.0] - 2026-10-29 @@ -469,6 +474,7 @@ and not implemented yet. - See the "Storage backend experiences" section of the README for provider-specific quirks found so far (e.g. Hetzner Storage Box sub-accounts). +[1.0.1]: https://github.com/dillardblom/ng_backup/releases/tag/v1.0.1 [1.0.0]: https://github.com/dillardblom/ng_backup/releases/tag/v1.0.0 [0.9.12]: https://github.com/dillardblom/ng_backup/releases/tag/v1.0.0-rc.6 [0.9.11]: https://github.com/dillardblom/ng_backup/releases/tag/v1.0.0-rc.5 diff --git a/PLAN.md b/PLAN.md index 89d2fd0..c3fd445 100644 --- a/PLAN.md +++ b/PLAN.md @@ -392,7 +392,7 @@ in README "Known limitations": gids (SFTP, Storage Box) → rc4 uitbrengen en om tests vragen → zelf een volledige DR van een productie-instantie van ~250 GB via S3 en via SMB. Drie volledige DR-restores vóór 1.0.0. Problemen of meldingen van gebruikers: rc5. -- **1.0.1:** alleen de kleine punten (besluit 2026-10-30): 4, 6–13. Punten 1, 2 en 5 gaan naar +- **1.0.1** (klaar voor release 2026-11-01): alleen de kleine punten (besluit 2026-10-30): 4, 6–13. Punten 1, 2 en 5 gaan naar 1.0.2 (README-roadmap aangepast); punt 3 is een test, ingepland voor de week van 2 november, niet aangekondigd en los van de release. 1. **Naar 1.0.2.** (Naar rc4: herstelsnelheid over SFTP.) S3 leest al 16 tegelijk bij index en tree, maar een diff --git a/README.md b/README.md index 87f1bf5..4cc95bd 100644 --- a/README.md +++ b/README.md @@ -7,7 +7,7 @@ installations and hosted Nextcloud. (Choosing SMB as a storage backend is the on see "Storage backend experiences" below — that requirement comes from files_external, not from ng_backup, and applies to any Nextcloud app that writes to an SMB share.) -**Status: 1.0.0, stable.** Disaster recovery has been tested on real installations (see "Tested +**Status: 1.0.1, stable.** Disaster recovery has been tested on real installations (see "Tested disaster recoveries" below). See "Known limitations" below, `PLAN.md` for the design and `docs/HOWTO.md` for a step-by-step guide from setup to a tested restore. Server lost? See `docs/DISASTER-RECOVERY.md`. @@ -260,15 +260,6 @@ What is planned, without dates. Ideas and votes are welcome in the [issues](https://github.com/dillardblom/ng_backup/issues); if something you need is listed here, a 👍 on its issue helps decide what comes first. -**1.0.1** -- An optional label for a backup started with "Back up now". -- An explanation in the trash of restore points of what "removed by retention policy" means and - until when a restore point can be brought back. -- A "Docs" tab on the admin page with links to the how-to, the disaster recovery guide and this - roadmap. -- Times in `occ` in the administrator's time zone, as on the admin page; restoring a single file - with `occ backup:restore --to-directory`. - **1.0.2** - A warning on the admin page and in `occ backup:status` when background jobs do not run on a system cron, with how to set one up. Without cron, a backup started with "Back up now" moves on diff --git a/appinfo/info.xml b/appinfo/info.xml index c23ce39..ed8ceb6 100644 --- a/appinfo/info.xml +++ b/appinfo/info.xml @@ -42,7 +42,7 @@ welcome: use the "Share your experience" link on the admin page. Developed and sponsored by [Ensembia](https://www.ensembia.com). We can offer (paid) assistance if you need help with restoring a backup after a crash.]]> - 1.0.0 + 1.0.1 agpl Dillard Blom NgBackup @@ -53,9 +53,9 @@ you need help with restoring a backup after a crash.]]> https://github.com/dillardblom/ng_backup https://github.com/dillardblom/ng_backup/issues https://github.com/dillardblom/ng_backup - https://raw.githubusercontent.com/dillardblom/ng_backup/v1.0.0/screenshots/1-backups.png - https://raw.githubusercontent.com/dillardblom/ng_backup/v1.0.0/screenshots/2-restore.png - https://raw.githubusercontent.com/dillardblom/ng_backup/v1.0.0/screenshots/3-settings.png + https://raw.githubusercontent.com/dillardblom/ng_backup/v1.0.1/screenshots/1-backups.png + https://raw.githubusercontent.com/dillardblom/ng_backup/v1.0.1/screenshots/2-restore.png + https://raw.githubusercontent.com/dillardblom/ng_backup/v1.0.1/screenshots/3-settings.png sodium