will/cateconners-campaigns
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Bump eec-campaigns pin to v0.1.6
Sync campaigns / sync (push) Successful in 16s
Details

Browse Source 
Sent/running campaigns are now skipped (not rejected) during sync, so a
finished campaign like 2026-07-23-iron-rose-proof-approved no longer has
to be deleted just to keep sync green.
This commit is contained in:
Will Estes
2026-08-13 13:25:17 -04:00
parent 3ace3f72dc
commit 79f6072cda
5 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+1 -1
View File
@@ -20,7 +20,7 @@ Alternatively, run the `Send campaign` workflow manually from Gitea Actions with
Repo secrets (Gitea Actions → Secrets) are already set: `CAMPAIGNS_LISTMONK_BASE_URL`, `CAMPAIGNS_LISTMONK_API_USER`, `CAMPAIGNS_LISTMONK_API_TOKEN`, `CAMPAIGNS_PREVIEW_EMAIL` (`hello@cateconners.com`, also a confirmed subscriber on `cateconners-list` so test-sends have somewhere to go) — scoped to a dedicated `campaigns-cateconners` listmonk API user (see `reground-infrastructure`'s `campaigns-cateconners` Ansible role).
The workflows in `.gitea/workflows/` pin a specific `eec-campaigns` version (currently `v0.1.5`). Bump that pin deliberately when a new tool version is ready, not automatically.
The workflows in `.gitea/workflows/` pin a specific `eec-campaigns` version (currently `v0.1.6`). Bump that pin deliberately when a new tool version is ready, not automatically.
## Sending as hello@cateconners.com