Repository navigation
ci: remove the Multitudes deployment notification - #477
Merged
Merged
Conversation
tobyhede
marked this pull request as ready for review
October 19, 2026 21:55
tobyhede
changed the title
tobyhede
force-pushed
the
claude/project-thread-2zuge0
branch
from
October 21, 2026 03:50
41d573e to
06aceb9
Compare
auxesis
approved these changes
Oct 21, 2026
auxesis
left a comment
auxesis
left a comment
Contributor
There was a problem hiding this comment.
Not sure why that PR check is stalled, but all looks good.
tobyhede
force-pushed
the
claude/project-thread-2zuge0
branch
from
October 21, 2026 05:11
06aceb9 to
17d4262
Compare
The Notify Multitudes step has failed every Release run on main since 2026-08-17 with a 500 from the Multitudes API, marking the Release workflow red even though the Docker image is built and published successfully. Remove the callback entirely. "Build (Rust MSRV)" is a required check on main, but the pull_request paths-ignore skipped the whole Test workflow for PRs that only touch release.yml or benchmark.yml, so the check was never reported and the PR could not merge. Always run the Test workflow on pull requests.
tobyhede
force-pushed
the
claude/project-thread-2zuge0
branch
from
October 21, 2026 05:58
c037312 to
dfc70ec
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Toby
Before: every Release run on
mainsince 2026-08-17 (runs 476 to 496) has finished red. The binaries and multi-platformcipherstash/proxy:mainimage are built and pushed successfully; the only failing step is the final "Notify Multitudes", wherePOST https://api.developer.multitudes.co/deploymentsreturns500 {"message":null}.After: the Multitudes deployment callback is gone, so the Release run reports its real outcome (did the image publish).
How: delete the "Notify Multitudes" step from
.github/workflows/release.yml. That step was the only reference to Multitudes in the repo.MULTITUDES_ACCESS_TOKENwas loaded from.github/secrets.env.encrypted, which is encrypted and isn't touched here; the now-unused entry there (and the token on the Multitudes side) can be revoked separately.Generated by Claude Code
Also: drop the
pull_requestpaths-ignorefrom.github/workflows/test.yml. "Build (Rust MSRV)" is a required check on main, and the filter skipped the whole Test workflow for PRs that only touchrelease.ymlorbenchmark.yml, so the check was never reported and those PRs could not merge. Thepushfilter on main is unchanged.Generated by Claude Code