chore(release): archied v1.37.0
This commit is contained in:
1 parent
25197a7941
commit
1b67340ce3
4 files changed
+95
No files matched your search
@@ -1,5 +1,48 @@
|
||||
# archied changelog
|
||||
|
||||
## [1.37.0] - 2026-09-22
|
||||
|
||||
### A request is attributed to the identity that made it
|
||||
|
||||
- **A browser can sign in, and an action taken through it records the person.** The dashboard validates a
|
||||
provider-issued token, resolves it to an identity, and attaches it to the request; the task-action record
|
||||
then names the actor. `Authenticate` and the sign-in callback share one resolver, so a browser sign-in
|
||||
cannot be accepted on terms a presented token would be refused on.
|
||||
- **archie issues no session.** The callback stores the provider's own token in an HttpOnly cookie and every
|
||||
later request re-verifies it, so nothing archie holds can outlive the provider's decision and there is no
|
||||
session table to expire, revoke or get wrong.
|
||||
- **The event kind describes the actor.** A person's approval records `human_approved` as that person; an
|
||||
agent's records `agent_approved`; an action with no authorising principal records `task_approved` with the
|
||||
attribution fields **empty**. Nothing is credited to an identity that did not act, and an unattributed
|
||||
action is recorded as unattributed rather than guessed.
|
||||
- The acting identity is derived from the presented credential and **never** from a request field: a body
|
||||
carrying `actor`, `actor_id`, `identity` and an `X-Archie-Actor` header still cannot choose it.
|
||||
|
||||
### A host install now works, and an update refuses a host it cannot keep consistent
|
||||
|
||||
- `install.sh` writes and enables **all five** host units; previously it seeded only `archied.service`, so a
|
||||
fresh host ran one service of five and an operator applied the rest by hand from a runbook. The runbook is
|
||||
a description again: it names the units and points at `systemctl --user cat`.
|
||||
- **Every host binary reports its version**, and the updater reads all of them **before it can report
|
||||
"nothing to install"**. A host whose binaries disagree is refused, naming each one: a newer messaging
|
||||
binary beside an older state store crash-loops against a service the older store does not serve, and that
|
||||
install previously looked healthy from the updater's point of view.
|
||||
- The packaged, installer and updater command lists are pinned by a test, so a service added to one and not
|
||||
the others fails the gate instead of shipping a partial install.
|
||||
|
||||
### A release image can be traced to a commit
|
||||
|
||||
- The publish step derives the commit by **dereferencing the ref** rather than reading `github.sha`, because
|
||||
every release tag in this repository is annotated and a tag's object id is not a commit. An immutable
|
||||
`sha-<commit>` tag is published alongside `:latest`, and a build with no release tag is stamped
|
||||
`dev+<short sha>` rather than a bare `dev` that identified nothing.
|
||||
|
||||
### Curator definitions are data, not a second registry
|
||||
|
||||
- Curator definitions may come from configuration or code and run through **one** engine into the existing
|
||||
registry — no parallel authority and no second config reader. A definition declares its tools, and an
|
||||
unknown tool name fails rather than widening the set silently.
|
||||
|
||||
## [1.36.0] - 2026-09-22
|
||||
|
||||
### The dashboard declares tools an in-browser agent can call
|
||||
|
||||
@@ -0,0 +1,44 @@
|
||||
# archied 1.37.0
|
||||
|
||||
Released 2026-09-22. [All news](../index.md)
|
||||
|
||||
### A request is attributed to the identity that made it
|
||||
|
||||
- **A browser can sign in, and an action taken through it records the person.** The dashboard validates a
|
||||
provider-issued token, resolves it to an identity, and attaches it to the request; the task-action record
|
||||
then names the actor. `Authenticate` and the sign-in callback share one resolver, so a browser sign-in
|
||||
cannot be accepted on terms a presented token would be refused on.
|
||||
- **archie issues no session.** The callback stores the provider's own token in an HttpOnly cookie and every
|
||||
later request re-verifies it, so nothing archie holds can outlive the provider's decision and there is no
|
||||
session table to expire, revoke or get wrong.
|
||||
- **The event kind describes the actor.** A person's approval records `human_approved` as that person; an
|
||||
agent's records `agent_approved`; an action with no authorising principal records `task_approved` with the
|
||||
attribution fields **empty**. Nothing is credited to an identity that did not act, and an unattributed
|
||||
action is recorded as unattributed rather than guessed.
|
||||
- The acting identity is derived from the presented credential and **never** from a request field: a body
|
||||
carrying `actor`, `actor_id`, `identity` and an `X-Archie-Actor` header still cannot choose it.
|
||||
|
||||
### A host install now works, and an update refuses a host it cannot keep consistent
|
||||
|
||||
- `install.sh` writes and enables **all five** host units; previously it seeded only `archied.service`, so a
|
||||
fresh host ran one service of five and an operator applied the rest by hand from a runbook. The runbook is
|
||||
a description again: it names the units and points at `systemctl --user cat`.
|
||||
- **Every host binary reports its version**, and the updater reads all of them **before it can report
|
||||
"nothing to install"**. A host whose binaries disagree is refused, naming each one: a newer messaging
|
||||
binary beside an older state store crash-loops against a service the older store does not serve, and that
|
||||
install previously looked healthy from the updater's point of view.
|
||||
- The packaged, installer and updater command lists are pinned by a test, so a service added to one and not
|
||||
the others fails the gate instead of shipping a partial install.
|
||||
|
||||
### A release image can be traced to a commit
|
||||
|
||||
- The publish step derives the commit by **dereferencing the ref** rather than reading `github.sha`, because
|
||||
every release tag in this repository is annotated and a tag's object id is not a commit. An immutable
|
||||
`sha-<commit>` tag is published alongside `:latest`, and a build with no release tag is stamped
|
||||
`dev+<short sha>` rather than a bare `dev` that identified nothing.
|
||||
|
||||
### Curator definitions are data, not a second registry
|
||||
|
||||
- Curator definitions may come from configuration or code and run through **one** engine into the existing
|
||||
registry — no parallel authority and no second config reader. A definition declares its tools, and an
|
||||
unknown tool name fails rather than widening the set silently.
|
||||
@@ -4,6 +4,7 @@ Release notes for archied and archie-agent, newest first.
|
||||
|
||||
## 2026-09-22
|
||||
|
||||
- [archied 1.37.0](archied/1.37.0.md)
|
||||
- [archied 1.36.0](archied/1.36.0.md)
|
||||
- [archied 1.35.0](archied/1.35.0.md)
|
||||
- [archied 1.34.0](archied/1.34.0.md)
|
||||
|
||||
@@ -1,4 +1,11 @@
|
||||
[
|
||||
{
|
||||
"component": "archied",
|
||||
"name": "archied",
|
||||
"version": "1.37.0",
|
||||
"date": "2026-09-22",
|
||||
"body": "### A request is attributed to the identity that made it\n\n- **A browser can sign in, and an action taken through it records the person.** The dashboard validates a\n provider-issued token, resolves it to an identity, and attaches it to the request; the task-action record\n then names the actor. `Authenticate` and the sign-in callback share one resolver, so a browser sign-in\n cannot be accepted on terms a presented token would be refused on.\n- **archie issues no session.** The callback stores the provider's own token in an HttpOnly cookie and every\n later request re-verifies it, so nothing archie holds can outlive the provider's decision and there is no\n session table to expire, revoke or get wrong.\n- **The event kind describes the actor.** A person's approval records `human_approved` as that person; an\n agent's records `agent_approved`; an action with no authorising principal records `task_approved` with the\n attribution fields **empty**. Nothing is credited to an identity that did not act, and an unattributed\n action is recorded as unattributed rather than guessed.\n- The acting identity is derived from the presented credential and **never** from a request field: a body\n carrying `actor`, `actor_id`, `identity` and an `X-Archie-Actor` header still cannot choose it.\n\n### A host install now works, and an update refuses a host it cannot keep consistent\n\n- `install.sh` writes and enables **all five** host units; previously it seeded only `archied.service`, so a\n fresh host ran one service of five and an operator applied the rest by hand from a runbook. The runbook is\n a description again: it names the units and points at `systemctl --user cat`.\n- **Every host binary reports its version**, and the updater reads all of them **before it can report\n \"nothing to install\"**. A host whose binaries disagree is refused, naming each one: a newer messaging\n binary beside an older state store crash-loops against a service the older store does not serve, and that\n install previously looked healthy from the updater's point of view.\n- The packaged, installer and updater command lists are pinned by a test, so a service added to one and not\n the others fails the gate instead of shipping a partial install.\n\n### A release image can be traced to a commit\n\n- The publish step derives the commit by **dereferencing the ref** rather than reading `github.sha`, because\n every release tag in this repository is annotated and a tag's object id is not a commit. An immutable\n `sha-<commit>` tag is published alongside `:latest`, and a build with no release tag is stamped\n `dev+<short sha>` rather than a bare `dev` that identified nothing.\n\n### Curator definitions are data, not a second registry\n\n- Curator definitions may come from configuration or code and run through **one** engine into the existing\n registry — no parallel authority and no second config reader. A definition declares its tools, and an\n unknown tool name fails rather than widening the set silently."
|
||||
},
|
||||
{
|
||||
"component": "archied",
|
||||
"name": "archied",
|
||||
|
||||
Reference in new issue
Block a user