Commit Graph
62 Commits
Author SHA1 Message Date
sam 53ba618b0b fix(sdk,semaphore): an action that may have run is an unknown outcome, not an error; retry a failed task status read (archie #2001)
publish / publish (push) Successful in 1m12s
2026-11-16 03:57:20 +11:00
sam 8df55d3225 fix(semaphore): refuse a template that would run on every host, and pass only declared variables (archie #2001)
publish / publish (push) Successful in 1m42s
2026-11-16 01:24:02 +11:00
sam f9234574bb feat(connectors): Semaphore connector, launching declared job templates once per idempotency key (archie #2001)
publish / publish (push) Successful in 1m6s
Each template the operator declares becomes an action with the effect declared
for it, so judgement decides on the declaration. A launch carries Archie's
idempotency key in the task message; invoking again finds that task instead of
launching another, so a resumed run never launches twice. A task that ends in
error is a known failure; one still running at the deadline is unknown.
2026-11-16 01:12:17 +11:00
sam 2928bdb682 fix(host): confine lookups to each host's configured path roots
publish / publish (push) Successful in 1m6s
Lookups run no guards and the helpers read as root, so an instruction injected
into an event could steer the agent into listing anywhere on the host. Each
host now names the roots its lookups may look under, and any other path is
refused before a command is built.
2026-11-16 00:42:48 +11:00
sam d74535c0d3 chore: use generic host names in test fixtures
publish / publish (push) Successful in 1m4s
2026-11-16 00:13:06 +11:00
sam b98620cc5b feat(host): root-owned read-only helpers behind a narrow sudo rule, and the target host's requirements
publish / publish (push) Successful in 1m4s
2026-11-15 23:11:18 +11:00
sam 645d514d11 fix(host): pin the host key's algorithm, so a host holding several keys matches its pin
publish / publish (push) Successful in 1m9s
2026-11-15 22:20:05 +11:00
sam 34bd70f1c1 feat(connectors): host connector with read-only SSH lookups; sops engine on the sops library
publish / publish (push) Successful in 2m53s
The host connector answers filesystem_usage, directory_sizes and old_files on
configured hosts over SSH with pinned host keys, dialling through the egress
tunnel when confined. The sops engine decrypts with the sops library instead
of the CLI, takes its file from settings and an age identity from its secrets.
2026-11-15 22:14:26 +11:00
sam 2c8bef237f refactor(connector): the SDK and Alertmanager connector use encoding/json/v2 and jsontext (archie #1980)
publish / publish (push) Successful in 56s
2026-11-15 18:11:38 +11:00
sam 7fd7a4104b feat(connector): the connector.v1 SDK and an Alertmanager connector (archie #1980)
publish / publish (push) Successful in 1m50s
2026-11-15 17:58:18 +11:00
sam 882a21596b feat(forge): report a close refused for open dependencies as a typed status (archie #1922)
publish / publish (push) Successful in 1m42s
2026-11-13 03:51:42 +11:00
sam a753d22e2b feat(forge): HasWriteAccess and issue author in the github and gitea extensions (archie #1830)
publish / publish (push) Successful in 2m1s
2026-11-09 12:39:12 +11:00
sam 186916d632 refactor(forge): drop ParseWebhook; forge webhooks arrive through archie's event capture (archie #1817)
publish / publish (push) Failing after 1s
2026-11-09 00:50:48 +11:00
sam 8f13cfe725 feat(forge/github): authenticate as a GitHub App and mint per-repository git credentials (archie #1817)
publish / publish (push) Failing after 1s
2026-11-09 00:14:02 +11:00
sam 4195ddc5bc ci: drop comments from workflow files
publish / publish (push) Successful in 46s
2026-11-08 16:55:04 +11:00
sam ea7e88d4b0 feat(channels): typed settings for email and telegram
publish / publish (push) Canceled after 13s
2026-11-08 16:16:50 +11:00
sam f55d78487d feat(channels): declare email and telegram settings for the dashboard form (archie #1796)
publish / publish (push) Successful in 1m14s
2026-11-08 15:50:34 +11:00
sam 9da3293592 ci(publish): name the missing DEPLOY_TOKEN instead of logging in with an empty password
publish / publish (push) Successful in 1m46s
Refs sam/archie#1785
2026-11-05 00:32:45 +11:00
sam 5864e725e4 fix(forge): empty label lists every open issue (archie #1770)
publish / publish (push) Successful in 1m21s
2026-11-03 08:12:06 +11:00
sam 6f28cf9013 feat(forge): bump gitea and github packages to 1.2.0 for CreateIssue
publish / publish (push) Successful in 1m6s
2026-11-03 02:43:25 +11:00
sam c722517353 feat(forge): add CreateIssue to the forge SDK, gitea and github plugins
publish / publish (push) Successful in 1m57s
Mirrors archie-core's proto/forge/v1 change: the SDK Forge interface and
server dispatch gain CreateIssue; gitea resolves label names to IDs
(creating missing labels) and github passes label names through.
2026-11-03 02:04:56 +11:00
sam d74c5f7421 docs(readme): tagline-first intro with verified entry-point links 2026-10-31 20:04:15 +11:00
sam 312b6e10cc ci: link new packages to the repository
publish / publish (push) Successful in 2m11s
2026-10-31 19:19:22 +11:00
sam 55ae2b6533 ci: publish packages and the catalogue to the Gitea registry
publish / publish (push) Successful in 2m19s
2026-10-31 18:19:52 +11:00
sam 86501fa1d4 feat(messaging): run Telegram as an archipelago channel extension (#1399)
The bundled internal/channels/telegram package (17 files) is deleted; the
channel now ships as archipelago/channels/telegram, launched by archiemessaging
through the existing channel-extension machinery. An existing [chat.telegram]
config enables it with the same keys: the token stays a secret reference
(token_ref) the host resolves, allowed_user_ids and show_tool_calls map onto
extension settings. Per-org bots compose the same extension per org from the
org's credential binding. Reload support is now derived from a channels.Reloader
interface instead of a *telegram.Gateway assertion. The five host-only seams
(/update, release announcements, running versions, in-place show_tool_calls,
reload) are dropped from the channel and need a contract home or deletion.
2026-10-31 15:30:27 +11:00
sam d03062cad8 test(forge): capture the submitted review object on GitHub and Gitea (#1166)
publish / publish (push) Failing after 36s
2026-10-31 14:34:55 +11:00
sam 176a74831f feat(forge/gitea): add ParseWebhook for signed Gitea deliveries (#279) 2026-10-31 14:33:35 +11:00
sam 5ff0c4d017 fix(catalogue): sign an issue time and refuse a replayed older catalogue 2026-10-29 23:27:34 +11:00
sam 60fbcd4c59 fix(forge): accept GitHub invitations only to configured repositories
AcceptInvitations accepted every pending repository invitation, so any
GitHub user could add the forge's account to a repository by sending an
invitation. The host now passes the connection's configured repositories
in AcceptInvitationsRequest and the extension leaves an invitation to
anything else pending. The Gitea forge is unchanged: it has no
invitations to accept.
2026-10-29 00:02:50 +11:00
sam 1c4ec39cd8 fix(bws): include the CLI's stderr in list failures 2026-10-27 15:23:54 +11:00
sam 3ee4977996 fix(age): read SSH keys and plugin identities, as the age CLI did
The switch to the age library read only native age keys, so an
AGE_IDENTITY holding an SSH private key or a plugin identity (a YubiKey)
stopped working. Both parse again; a plugin that asks for input fails with
a message saying so, and a passphrase-protected identity file is refused
by name.
2026-10-25 18:13:27 +11:00
sam 2d475e281f fix(secret-engines): report a missing key as not found; age and Vault need no CLI
The age, Vault and SOPS engines shelled out with stderr discarded, so a
missing key and a broken setup both surfaced as 'exit status 1' and were
reported as the engine being unavailable. age now decrypts with the age
library and Vault reads over its API (KV v1 or v2, detected as the CLI
does), so neither needs a CLI on the host. SOPS still uses the CLI, whose
library would pull in every cloud KMS SDK, but decrypts the whole file to
JSON and looks the key up itself, so the key never reaches the CLI.
2026-10-25 18:11:39 +11:00
sam 16b832be4c fix(bws): refresh secrets and retry a failed read instead of caching the first result forever
The engine listed secrets once per process. A failed first read made every
key unavailable until a restart, and a rotated or added secret never showed.
The list is now cached for five minutes, re-read sooner for a missing key,
never cached on failure, and a stale value is served while a refresh fails.
2026-10-25 18:11:39 +11:00
sam b1ee58c1b8 fix(email): retry mail after a transient failure, ignore automatic mail, thread replies
A gateway or SMTP failure skipped the message for the life of the process,
so mail sent during an outage was never answered. Only mail the channel
rejects is skipped now; the rest is retried on the next poll, and the
Message-ID as the source id makes the gateway replay a reply it already
produced instead of running the turn twice. Out-of-office replies, bulk and
list mail are ignored and replies are marked Auto-Submitted, so the channel
cannot loop with an auto-responder. Replies carry References for threading,
and port 465 uses implicit TLS.
2026-10-25 18:11:39 +11:00
sam 5f9eda24f5 fix(gitea): honour each call's context, SDK branch linking, real 404s, paginated labels
Every call shared one SDK client whose context was background, so no caller
could cancel a Gitea request; each call now binds its own. LinkBranch
hand-built JSON over raw HTTP and posted to an endpoint Gitea does not have;
it sets the issue's ref through the SDK. PRState and VerifyPush matched error
text instead of the status, label lookup stopped at the first 100 labels,
merges ignored the repository's merge style, and a review of the token's own
pull request requested changes Gitea refuses.
2026-10-25 18:11:39 +11:00
sam 45bd6c47ee fix(github): readable API errors, normalised webhook review states, no REQUEST_CHANGES on the token's own PR
Errors say what GitHub refused in its own words instead of the request URL
and an empty field list. Webhook review states arrive lower-case and were
never normalised, so a webhook-delivered change request did not read as one.
A review the token would post as REQUEST_CHANGES on its own pull request
comments instead, which GitHub accepts. Secondary rate limits wait up to two
minutes and retry.
2026-10-25 18:11:39 +11:00
sam ed82b6811e fix(forge): allow the GitHub extension to download archives from codeload (#1)
* fix(forge): keep the archive download token out of errors

* fix(forge): allow the GitHub extension to download archives from codeload
2026-10-19 15:48:22 +11:00
sam e1377fbe98 fix(packages): drop the surface word from display names 2026-10-17 22:41:11 +11:00
sam d8b23f61c0 fix(forge): name the forges GitHub and Gitea 2026-10-17 22:26:37 +11:00
sam eb676c7134 feat(forge): submit one review with event and body on GitHub and Gitea 2026-10-17 21:23:33 +11:00
sam 931622ce39 chore(sdk): regenerate gateway stubs with logging; stop buf clean wiping hand-written SDK 2026-10-17 21:23:33 +11:00
sam 35009a16e2 fix(bws): declare the Bitwarden API hosts the bws CLI reaches 2026-10-07 21:49:54 +11:00
sam 0a31a10449 docs: catalogue publishing and one-click install 2026-10-06 01:21:21 +11:00
sam 1fa1b2583c feat(scripts): publish every package to GHCR with a signed catalogue; reproducible package layers 2026-10-06 01:21:15 +11:00
sam ee9271e7cf feat(forge): MergePR on the SDK, GitHub and Gitea forges 2026-10-05 21:36:07 +11:00
sam ca1bd1de11 feat(forge): ClosePR on the SDK, GitHub and Gitea forges 2026-10-05 20:11:43 +11:00
sam 6c2f1b20dd test(secret-engines/vault): table-test key validation 2026-10-05 18:24:57 +11:00
sam 0c27e9b8a5 fix(secret-engines/vault): refuse keys that would become CLI flags; document extension safety rules 2026-10-05 18:24:47 +11:00
sam 6ecbc2f006 fix(channels/email): leave ignored mail unread; keep version 1.0.0 2026-10-05 18:22:29 +11:00
sam ea97517182 fix(channels/email): ignore the IMAP close error explicitly 2026-10-05 18:16:28 +11:00