From afea828e41fc147644117e3d4e7ee0c3f7b7ab41 Mon Sep 17 00:00:00 2001 From: Teg79 Date: Thu, 19 Nov 2026 18:07:07 +0100 Subject: [PATCH 1/2] docs(changelog): what merged since 0.1.0 - Forgejo (breaking for 0.1.0 platforms), urbex updates, the ledger and urbex-op fixes Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_0182yxsfwRowwnxCfgrQwjnA --- CHANGELOG.md | 47 +++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 47 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 31292a1..6bbf926 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -18,6 +18,53 @@ workflow refuses a tag whose version has no entry here. ## [Unreleased] +### Breaking + +- **The forge is Forgejo 15 LTS** in place of Gitea 1.24 (urbforge/urbex + ADR-0034, #116). A platform installed with 0.1.0 runs Gitea 1.24, whose + database Forgejo can't open: on such a platform `urbex bootstrap` with + this release starts Forgejo on Gitea's data, Forgejo exits ("Your + database (migration version: 321) is for a newer Forgejo") without + changing it, and the forge stays down. Gitea's data is untouched. + +### Upgrading + +- From 0.1.0: don't run `urbex bootstrap` on the existing platform. Tear + it down and bootstrap again (`urbex teardown`, then `urbex bootstrap`; + the repositories are pushed again from your clones), or stay on 0.1.0. + The workspace needs no change: the credentials and the platform config + written by 0.1.0 are still read (`giteaAdminPassword`, `giteaToken`, + `git.giteaUrl`); the new names (`forgeAdminPassword`, `forgeToken`, + `git.forgeUrl`) win when both are there. + +### Added + +- **`urbex updates []`** (#119): for each application from a + published image, whether a newer image is available - the tag asked + for moved (`urbex deploy --update`), a newer minor or patch + (`urbex deploy --app --version `), a new major + (listed, not proposed). The tags come from the registry, anonymously. + +### Changed + +- The forge is Forgejo 15 LTS, pinned by digest, and "forge" replaces + "Gitea" where the name is generic: messages, `urbex status`, the + credentials and the platform config (see Breaking and Upgrading). The + LXC, Stack and volume keep their names (`urbex-gitea`, `gitea-data`) + (#116). +- Releases carry their notes from this file, and fail without them + (#118). + +### Fixed + +- `urbex-op` never pulls an image built locally (`localhost/...`, or + docker's bare name): it says how to build it instead (#117). +- The allocation ledger frees the addresses of machines that are gone: + `urbex apply` for an application removed from `urbex.yaml`, `urbex + destroy` for every machine of the environment's state; `urbex teardown` + forgets stale entries whose machine is no longer on Proxmox, and names + those that still are (#120). + ## [0.1.0] - 2026-11-17 The first preview release: urbex as binaries for Linux and macOS (amd64, From d8073433cf4f44250f3f3d093f9b3374f06feb57 Mon Sep 17 00:00:00 2001 From: Teg79 Date: Thu, 19 Nov 2026 18:14:18 +0100 Subject: [PATCH 2/2] docs(changelog): Forgejo's breaking change with bootstrap's refusal (#134), and the upgrade from 0.1.0 Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_0182yxsfwRowwnxCfgrQwjnA --- CHANGELOG.md | 24 +++++++++++++----------- 1 file changed, 13 insertions(+), 11 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 6bbf926..7fe1aef 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -22,20 +22,22 @@ workflow refuses a tag whose version has no entry here. - **The forge is Forgejo 15 LTS** in place of Gitea 1.24 (urbforge/urbex ADR-0034, #116). A platform installed with 0.1.0 runs Gitea 1.24, whose - database Forgejo can't open: on such a platform `urbex bootstrap` with - this release starts Forgejo on Gitea's data, Forgejo exits ("Your - database (migration version: 321) is for a newer Forgejo") without - changing it, and the forge stays down. Gitea's data is untouched. + database Forgejo can't open, so it can't move to this release in place: + `urbex bootstrap` sees that its forge is Gitea and refuses, changing + nothing (#134). ### Upgrading -- From 0.1.0: don't run `urbex bootstrap` on the existing platform. Tear - it down and bootstrap again (`urbex teardown`, then `urbex bootstrap`; - the repositories are pushed again from your clones), or stay on 0.1.0. - The workspace needs no change: the credentials and the platform config - written by 0.1.0 are still read (`giteaAdminPassword`, `giteaToken`, - `git.giteaUrl`); the new names (`forgeAdminPassword`, `forgeToken`, - `git.forgeUrl`) win when both are there. +- From 0.1.0: start the platform again to get this release's platform, + the Java4Shell mitigation included. Back up the applications' named + volumes, `urbex destroy` every environment, `urbex teardown --yes`, then + `urbex bootstrap` with this release, push the projects' repositories + again and `urbex apply` their environments (urbforge/urbex + `docs/upgrading.md`, *From 0.1.0 to 0.2.0*). Or keep 0.1.0 on that + platform. The workspace needs no change: the credentials and the + platform config written by 0.1.0 are still read (`giteaAdminPassword`, + `giteaToken`, `git.giteaUrl`); the new names (`forgeAdminPassword`, + `forgeToken`, `git.forgeUrl`) win when both are there. ### Added