{ "id": "a23c3499ac904060471778ddb576f79fd42a5e4e02bf5937aa70469c478b9d65", "pubkey": "a008def15796fba9a0d6fab04e8fd57089285d9fd505da5a83fe8aad57a3564d", "created_at": 1788907178, "kind": 30063, "tags": [ [ "a", "32267:a008def15796fba9a0d6fab04e8fd57089285d9fd505da5a83fe8aad57a3564d:ngit-ci", "wss://relay.ngit.dev" ], [ "i", "ngit-ci" ], [ "version", "0.1.1" ], [ "d", "[email protected]" ], [ "c", "main" ], [ "e", "487c6ec3af677eef7127145c6db45bf6a47deb0c04dd5b4131d360a68fbe02b3", "wss://relay.ngit.dev" ], [ "e", "c3d848aa2df935e9c9cd3fae80511cfa26d013c27c84e82211b78073162b05ae", "wss://relay.ngit.dev" ], [ "f", "linux-x86_64" ], [ "commit", "aab453f92c8ee239442e78a3e5a761fa6201d5ab" ] ], "content": "Version 0.1.1 is the first ngit-ci release published through Nostr with NIP-82,\nso its release notes include the full overview of the 0.1 release line as well\nas the fixes found while validating the first production tag run.\n\nngit-ci is the reference coordinator for the NIP-C1 Nostr CI protocol. It\nprovides a complete self-hosted path from discovering NIP-34 repository\nactivity to executing workflows and publishing signed results over Nostr.\n\nHighlights delivered across the 0.1 release line include:\n\n- **Nostr-native coordination:** coordinator advertisements, repository status,\n maintainer-controlled Service Requests and Stops, manual triggers, and signed\n progress, job, and workflow results.\n- **Workflow execution and isolation:** GitHub Actions-compatible workflows run\n through `act` in containers or in disposable QEMU/KVM microVMs through the\n Loom execution-adapter contract, with capability-aware claiming,\n trust-scoped caches, and queue recovery across graceful restarts.\n- **Logs, artifacts, and outputs:** per-job results and diagnostics, optional\n Blossom publication of full logs and artifacts, workflow artifact transfer,\n public job outputs, lifecycle timing, and distinct failure conclusions.\n- **Repository-scoped secrets:** operator provisioning, encrypted updates over\n Nostr, current-maintainer authorization, optional NIP-46 bunker sealing, and\n authenticated access to private GitHub inputs for Nix builds.\n- **Current NIP-34 roles:** authorization follows confirmed `M` and `m`\n maintainer relationships, lead handovers, departures, and the non-maintainer\n `o` moderator role.\n- **Deployment and documentation:** Docker and Compose, Proxmox/LXC, NixOS,\n portable Linux archives published as signed NIP-82 assets, and a complete\n in-repository set of workflow-author, operator, security, architecture,\n deployment, testing, and protocol documentation.\n\nOperators upgrading from an earlier prerelease should note that ordinary push\nand pull-request execution now defaults to `request-required`. The RC.2 entry\nbelow gives the required migration options.\n\n### Fixed\n\n- Tag-triggered act checkouts now materialize the exact lightweight or\n annotated tag ref from signed trigger state while retaining a depth-one\n fetch, making tag metadata available to workflows and NIP-82 publication.\n- The NIP-82 application metadata now includes an icon, allowing unattended\n tag releases to satisfy the manifest's strict metadata policy.", "sig": "c593331856fdaa2e38d6fa450049602cc8d49fd6035a92ed8fa585e2214a7d543c1b79586c55b23f0cf7dc49baa8b559d3f4103269c3cb7e3a48037e11f36128" }