lfg2025/archy
1
0
Fork 0
Code Issues 16 Pull Requests Actions Packages Projects Releases 44 Wiki Activity
archy/releases/manifest.json

26 lines
1.0 KiB
JSON
Raw Normal View History

feat: add community infrastructure and update server setup - releases/manifest.json: Seed release manifest for update server - update.rs: Make UPDATE_MANIFEST_URL configurable via ARCHIPELAGO_UPDATE_URL env var - CONTRIBUTING.md: Comprehensive contribution guidelines covering code style, PR process, testing, security disclosure, and app submission - .github/ISSUE_TEMPLATE/: Bug report, feature request, and app submission issue templates with structured forms - .github/pull_request_template.md: PR template with checklist Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-11 10:57:33 +00:00
{
release(v1.7.1-alpha): version bump for end-to-end OTA test Trivial bump on top of df83163f. No code changes — this exists purely so the fleet nodes now sitting on 1.7.0-alpha have a real target to exercise the OTA pipeline against: check → download → apply → restart → state reconciliation. The binary content differs only in the embedded CARGO_PKG_VERSION string. Frontend tarball reused from v1.7.0-alpha (same bytes, copied to a new filename to match the manifest component name convention). Artefacts: archipelago 7f7981bd…56eef0 40391760 archipelago-frontend-1.7.1-alpha.tar.gz (dup of 1.7.0) dc3b63af…e9a8370 76984288 Manifest changelog is a single plain-language sentence explaining that this is the test release — per the saved feedback about keeping fleet-facing strings readable. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-20 10:32:06 -04:00
"version": "1.7.1-alpha",
release(v1.7.0-alpha): bump + fix git-method update + reconciler creates Two fixes bundled into the OTA: 1. update.download hard-fail on git-path nodes. handle_update_check's git branch reported update_available=true + update_method="git" but never populated state.available_update, so update.download returned "No update available to download" even though the UI showed one. SystemUpdate.vue now routes update_method=="git" through update.git-apply (pull+rebuild+ restart via self-update.sh); manifest-path nodes keep the download→apply flow. i18n strings + confirm modal added for the git path. 2. Reconciler creating containers behind the user's back. On fresh unbundled installs (.198, .253) archy-mempool-db and archy-btcpay-db materialised ~10 min after first boot because reconcile-containers.sh walked container-specs.sh's canonical tier list and created any "missing" container. reset_spec() now defaults SPEC_OPTIONAL="true", so reconcile is strictly a repair tool — baseline comes from first-boot-containers.sh (filebrowser on unbundled), everything else from the install RPC. Also forces OTA trigger for nodes on 1.6.0-alpha that otherwise saw "I'm at manifest.version, nothing to do" and skipped the refreshed 1.6 artifacts. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-20 06:22:29 -04:00
"release_date": "2026-04-20",
feat: add community infrastructure and update server setup - releases/manifest.json: Seed release manifest for update server - update.rs: Make UPDATE_MANIFEST_URL configurable via ARCHIPELAGO_UPDATE_URL env var - CONTRIBUTING.md: Comprehensive contribution guidelines covering code style, PR process, testing, security disclosure, and app submission - .github/ISSUE_TEMPLATE/: Bug report, feature request, and app submission issue templates with structured forms - .github/pull_request_template.md: PR template with checklist Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-11 10:57:33 +00:00
"changelog": [
release(v1.7.1-alpha): version bump for end-to-end OTA test Trivial bump on top of df83163f. No code changes — this exists purely so the fleet nodes now sitting on 1.7.0-alpha have a real target to exercise the OTA pipeline against: check → download → apply → restart → state reconciliation. The binary content differs only in the embedded CARGO_PKG_VERSION string. Frontend tarball reused from v1.7.0-alpha (same bytes, copied to a new filename to match the manifest component name convention). Artefacts: archipelago 7f7981bd…56eef0 40391760 archipelago-frontend-1.7.1-alpha.tar.gz (dup of 1.7.0) dc3b63af…e9a8370 76984288 Manifest changelog is a single plain-language sentence explaining that this is the test release — per the saved feedback about keeping fleet-facing strings readable. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-20 10:32:06 -04:00
"Over-the-air update test — same features as 1.7.0, just a fresh version number so your node can try the new download-and-apply flow end-to-end. Safe to apply; nothing to do afterwards."
feat: add community infrastructure and update server setup - releases/manifest.json: Seed release manifest for update server - update.rs: Make UPDATE_MANIFEST_URL configurable via ARCHIPELAGO_UPDATE_URL env var - CONTRIBUTING.md: Comprehensive contribution guidelines covering code style, PR process, testing, security disclosure, and app submission - .github/ISSUE_TEMPLATE/: Bug report, feature request, and app submission issue templates with structured forms - .github/pull_request_template.md: PR template with checklist Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-11 10:57:33 +00:00
],
chore: update release manifest to v1.3.5 Nodes can now see v1.3.5 as an available update. Includes registry migration changelog and component download URLs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-11 10:29:21 -04:00
"components": [
{
"name": "archipelago",
release(v1.7.1-alpha): version bump for end-to-end OTA test Trivial bump on top of df83163f. No code changes — this exists purely so the fleet nodes now sitting on 1.7.0-alpha have a real target to exercise the OTA pipeline against: check → download → apply → restart → state reconciliation. The binary content differs only in the embedded CARGO_PKG_VERSION string. Frontend tarball reused from v1.7.0-alpha (same bytes, copied to a new filename to match the manifest component name convention). Artefacts: archipelago 7f7981bd…56eef0 40391760 archipelago-frontend-1.7.1-alpha.tar.gz (dup of 1.7.0) dc3b63af…e9a8370 76984288 Manifest changelog is a single plain-language sentence explaining that this is the test release — per the saved feedback about keeping fleet-facing strings readable. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-20 10:32:06 -04:00
"current_version": "1.7.0-alpha",
"new_version": "1.7.1-alpha",
"download_url": "https://git.tx1138.com/lfg2025/archy/raw/branch/main/releases/v1.7.1-alpha/archipelago",
"sha256": "7f7981bdf33af6fdb0022338c62e0a102b17c1da95f87f630b07fc2b6056eef0",
"size_bytes": 40391760
chore: update release manifest to v1.3.5 Nodes can now see v1.3.5 as an available update. Includes registry migration changelog and component download URLs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-11 10:29:21 -04:00
},
{
release(v1.7.1-alpha): version bump for end-to-end OTA test Trivial bump on top of df83163f. No code changes — this exists purely so the fleet nodes now sitting on 1.7.0-alpha have a real target to exercise the OTA pipeline against: check → download → apply → restart → state reconciliation. The binary content differs only in the embedded CARGO_PKG_VERSION string. Frontend tarball reused from v1.7.0-alpha (same bytes, copied to a new filename to match the manifest component name convention). Artefacts: archipelago 7f7981bd…56eef0 40391760 archipelago-frontend-1.7.1-alpha.tar.gz (dup of 1.7.0) dc3b63af…e9a8370 76984288 Manifest changelog is a single plain-language sentence explaining that this is the test release — per the saved feedback about keeping fleet-facing strings readable. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-20 10:32:06 -04:00
"name": "archipelago-frontend-1.7.1-alpha.tar.gz",
"current_version": "1.7.0-alpha",
"new_version": "1.7.1-alpha",
"download_url": "https://git.tx1138.com/lfg2025/archy/raw/branch/main/releases/v1.7.1-alpha/archipelago-frontend-1.7.1-alpha.tar.gz",
feat(identity,update): default avatars, public blobs, long-running downloads Follow-up to 1fb71b4b on the same v1.7.0-alpha line. Identity avatars • New module `avatar.rs` generates two deterministic SVG styles keyed off the pubkey: a 5×5 mirrored identicon for sub-identities and a hexagonal-network motif for the master (seed index 0) identity. Both returned as base64 data URLs, so a fresh identity has a recognisable picture before the user uploads anything. • `IdentityManager::create()` and `create_from_seed()` populate `profile.picture` on creation. Index 0 gets the node SVG; all other seed-derived + ad-hoc identities get the identicon. Blob store — public flag for profile assets • `BlobMeta.public` (default false) added; `BlobStore::put()` takes a `public: bool`. Missing in legacy meta files = false. • `POST /api/blob` now stores uploads with public=true and returns `public_url` alongside `self_test_url`. public_url is `http://<node-onion>/blob/<cid>` (no cap) if Tor has published the archipelago hidden service, else falls back to the local path. • `GET /blob/<cid>` bypasses the HMAC capability check when the requested blob is flagged public — external Nostr clients fetching a kind-0 `picture` URL can't hold a cap. • Mesh callers (content_ref attachments, dispatch rehydration) pin public=false explicitly so nothing leaks out of the mesh path. Profile editor UX • Collapsed Save + Save & Publish into one button — the Save action now persists locally AND publishes the kind-0 metadata event in one step. Uploads store `public_url` into `profile.picture` / `profile.banner` so the published URL is reachable by external clients. Update client — the 15-second cliff • Frontend `rpcClient.call` for `update.download` now has an explicit 30-minute timeout (was falling back to the default 15 s). `update.apply` gets 5 min, `update.git-apply` gets 15 min. Matches what the backend is actually willing to wait for. • Backend `load_state()` reconciles `state.current_version` with `CARGO_PKG_VERSION` on every start. Sideloaded or reflashed nodes were stuck advertising the old version even with a new binary in place, which kept re-offering the same release as an update. Manifest changelog rewritten for fleet readers per the saved feedback (no function names, no file paths). Artefacts refreshed: binary 12f838c5…5ba82d 40381864 frontend dc3b63af…e9a8370 76984288 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-20 10:03:38 -04:00
"sha256": "dc3b63afedc45a663a023702ea23b6ac499d5b2731078a9b5a2feb57ae9a8370",
"size_bytes": 76984288
chore: update release manifest to v1.3.5 Nodes can now see v1.3.5 as an available update. Includes registry migration changelog and component download URLs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-11 10:29:21 -04:00
}
]
feat: add community infrastructure and update server setup - releases/manifest.json: Seed release manifest for update server - update.rs: Make UPDATE_MANIFEST_URL configurable via ARCHIPELAGO_UPDATE_URL env var - CONTRIBUTING.md: Comprehensive contribution guidelines covering code style, PR process, testing, security disclosure, and app submission - .github/ISSUE_TEMPLATE/: Bug report, feature request, and app submission issue templates with structured forms - .github/pull_request_template.md: PR template with checklist Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-11 10:57:33 +00:00
}
Reference in New Issue Copy Permalink