Skip to main content
← Back to list
01Issue
BugShippedSwamp ClubPublicTeam
Assigneeskeeb

Relationships

#1127 New Release Discord notification links to GitHub Actions run instead of swamp changelog/release notes

Opened by mgreten · 7/13/2026· Shipped 8/24/2026

The "New Release" message posted by Swamp Bot to the #automated-activity Discord channel links to a GitHub Actions run instead of the actual swamp changelog / release notes page.

Example:

New Release Swamp CLI 20260713.225646.0-sha.39b472d2 has been released swamp-club.com

Posted today at 5:13 PM in #automated-activity, but the link target is: https://github.com/swamp-club/swamp/actions/runs/29291561777

That's the internal CI build run for the release, not a page a user should be looking at — it's not the release notes/changelog, and it's a link into private CI infra rather than the public swamp-club.com site the message text implies ("swamp-club.com" is shown as the link source).

Expected: the link should point at the actual release notes / changelog entry for that version (e.g. a swamp-club.com/releases/ page or equivalent), not the GitHub Actions run URL.

Repro: any tagged CLI release triggers this notification via the release workflow; check whichever job posts to the automated-activity Discord webhook for where it builds the link URL.

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 4 MOREREVIEW+ 4 MOREPR_MERGED+ 1 MORECONTRIBUTOR_NOTIFIED

Shipped

8/24/2026, 9:08:42 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
keeb assigned keeb8/24/2026, 8:25:50 PM
Editable. Press Enter to edit.

mgreten commented 7/23/2026, 9:32:47 PM

keeb commented 8/24/2026, 9:08:47 PM

Thanks @mgreten for reporting this! The fix has been merged and a release is on its way. We appreciate your contribution to swamp.

keeb commented 8/24/2026, 9:09:21 PM

Shipped — PR #1134, discord-bot deployed to DOKS at 7bcc3c5c.

Root cause. The run_id on the event comes from swamp-uat's uat.yml as $GITHUB_RUN_ID — a run in the swamp-uat repo — while the template pasted it into an Actions URL for the swamp repo. A run id from one repository in another's URL. Verified against the live API: it 404s. It has never resolved for anyone, since the template's first and only commit on 2026-04-04. swamp-uat is also private, so even a well-formed link is a dead end for a public channel.

On the requested fix. There is no release-notes page on swamp-club.com to point at (/changelog is a vanity alias to the podcast campaign), so the link was removed rather than repointed.

In its place, the embed now carries a one-line headline of what shipped — the merged PR title the release pipeline already writes, with the issue refs and conventional-commit prefix stripped:

New Release Swamp CLI 20260824.164253.0-sha.8d1ce768 has been released Use run-scoped model names to prevent lock contention

Guard. url is now optional in template frontmatter, and template-engine_test.ts sweeps all 14 templates: no unresolved variable survives, any url present is https on swamp-club.com, and every template file must have a fixture. There was no test over templates at all — that is how this lived four months.

One part deliberately not shipped here. The headline's source is two small diffs in swamp-club/swamp and swamp-club/swamp-uat, which this repo cannot ship. Until one lands the embed renders the version line alone — correct and link-free, which is the bug you reported.

Thanks for the report, @mgreten — the detail that it was an internal CI URL rather than just a wrong page is what made the two-repo mismatch findable.

keeb commented 8/24/2026, 9:16:43 PM

Follow-up filed as #1806 — the emitter half (swamp-uat's uat.yml sending the PR title as headline), which is what turns the version-only announcement into one that says what shipped. Diffs for both options are in that issue.

mgreten commented 8/24/2026, 10:27:26 PM

Thank you @keeb!

keeb commented 8/24/2026, 10:44:47 PM

🫡

Sign in to post a ripple.