mix
75207f0d1e
[1.0.0]
Added:
- A **Delivery log** on each delivery's page (`/deliveries/{id}`): the
- A **History** block on the same page: the journal's two timestamps stated as
Fixed:
- Postfix config: copy TLS cert/key from the (often `:ro`, host-owned) mount
- Postfix config: allow `maillog_file` under `/data` via
- E2e: read `/data/setup-token` via `docker compose exec` (file is `0600`
- Entrypoint: check `SELFPOST_HOSTNAME` before `/data` setup (so a bad identity
- E2e gate: wait for host-published `/healthz` before panel setup, and stop
… (3 more in CHANGELOG)
Changed:
- Document what `.spbk` and `.spde` stand for (SelfPost backup / SelfPost domain
- Docs aligned with the code: setup URL is `/setup/<token>` (README and
- Full backups no longer carry `/data/log`. It is Postfix's raw log plus its
- Monitoring screens (status, mail queue, system log, deliveries) use adaptive
- Documentation package consolidated into `docs/development.md`: Documentation
… (4 more in CHANGELOG)
[1.0.1]
A documentation and packaging release: no change to the mail path, the database, or the on-disk layout. Upgrading is a tag bump.
Added:
- `SECURITY.md` — how to report a vulnerability privately (GitHub private
- [docs/plans/](docs/plans/) — one document per agreed extension: the optional
Changed:
- The panel's **Account** entry is now called **Settings** — nav link, page
- The signed-in name in the panel's nav is now labelled `User:`, so it reads as
- [docs/product.md](docs/product.md) reframes the future line: the inbound
- [docs/security.md](docs/security.md) is now in English, matching the rest of
- The README documentation table now points at `SECURITY.md` for reporting a
… (2 more in CHANGELOG)
Fixed:
- The panel's static assets are served with a content ETag and
Squashed CHANGELOG sections: [1.0.0], [1.0.1].
Full detail: CHANGELOG.md (1.0.0, 1.0.1).
25 lines
1.0 KiB
Plaintext
25 lines
1.0 KiB
Plaintext
---
|
|
description: Agent rules for the SelfPost repository (formerly spec §12)
|
|
alwaysApply: true
|
|
---
|
|
|
|
# Agent rules
|
|
|
|
1. **No git commits** without an explicit instruction in the prompt.
|
|
2. After Go changes: `go build`, `go vet`; fix all issues. Run `go test` when
|
|
tests exist.
|
|
3. Before calling a container task done: the image builds and the container starts.
|
|
4. Iterate: minimal skeleton first, then features.
|
|
5. Security requirements — `docs/security.md`; implement with the feature, not deferred.
|
|
6. Do not implement out-of-scope items (`docs/product.md`); do not change fixed
|
|
assumptions without agreement.
|
|
7. For large tasks: propose a plan before coding unless the user already approved one.
|
|
8. Check licence compatibility of new Go dependencies (permissive or GPL-family for
|
|
AGPL-3.0).
|
|
|
|
Model routing — `docs/development.md` § «Model routing». Pre-release security
|
|
**review** (not authorship) — Fable.
|
|
|
|
Commit protocol, CHANGELOG, and phase closure — `docs/development.md` §
|
|
«Commits and release build» and «Phase closure».
|