Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -70,13 +70,13 @@ jobs:
# Writes dist/packages/*.orax (one per target in bundle.config.ts) and dist/manifest.toml,
# reproducing exactly what upstream.lock.json records and verifying every download against it.
# With `--agent-configuration` every package carries assets/config.json, the Agent
# declaration, and the release binds it; the flag waits until the Ora hosts that resolve
# the declaration are deployed — current hosts install an `agent`-kind package carrying
# it but then refuse to activate the plugin, so the bytes must not ship early.
# declaration, and the release binds it. A host that cannot compile the declaration installs
# such a package but then refuses to activate the plugin; the owner turned the flag on once
# the hosts that resolve it were accepted, so every release from here on ships it.
- name: Package
env:
TAG: ${{ inputs.tag || github.ref_name }}
run: deno task package --tag "$TAG" --repo "${{ github.repository }}"
run: deno task package --tag "$TAG" --repo "${{ github.repository }}" --agent-configuration

- name: Create release
env:
Expand Down
7 changes: 4 additions & 3 deletions AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -260,9 +260,10 @@ packages carry no declaration at all and current hosts install the release
exactly as before. With it, the static copy (`dist/agent-configuration.json`,
attached to the release and copied into the registry entry beside `orax.toml`)
and the `[agent_configuration]` section in `manifest.toml` are written alongside
the bytes. `release.yml` passes the flag only once the hosts resolving the
declaration are deployed; that is an owner decision made by editing one line,
not something this repository can detect.
the bytes. `release.yml` passes the flag: the owner turned it on once the hosts
resolving the declaration were accepted. That is an owner decision made by
editing one line, not something this repository can detect, and turning it back
off is the same one-line edit.

The packaging script deliberately does not interpret the declaration's shape: it
checks readable UTF-8, the 256 KiB size bound every host enforces, and reads
Expand Down
Loading