ci: notify Slack when a prerelease publishes - #24
Merged
Conversation
The prerelease job only pinged Slack on failure, on the reasoning that a message per merge would be noise. In practice that made a successful prerelease invisible: 1.0.21-next.4f1def5 published cleanly and the first anyone knew of it was by checking npm by hand. Silence is the wrong default here. A prerelease exists to be tried, and nobody tries what they are not told about. The success message names the version, gives the command to install it, states that `latest` is untouched and at what, and links the commit and author. A re-run of an already-published commit gets its own line rather than borrowing the success one — it publishes nothing, and a message saying otherwise would be a lie for anyone reading the channel.
NejcS
approved these changes
Aug 28, 2026
NejcS
left a comment
NejcS
left a comment
Contributor
There was a problem hiding this comment.
You probably did already but just make sure that the secret's there. Can we have secrets in a public repo anyway?
Collaborator
Author
@NejcS we can. Those secrets arent visible to outsiders. |
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.
The prerelease job only pinged Slack on failure — my call when I wrote it, on the reasoning that a message per merge would be noise. In practice it made a successful prerelease invisible:
1.0.21-next.4f1def5published cleanly (run33171274338) and the first anyone knew of it was checking npm by hand.Silence is the wrong default here. A prerelease exists to be tried, and nobody tries what they aren't told about.
What lands in Slack now
Published:
Nothing to publish (a re-run of an already-published commit) gets its own line rather than borrowing the success one — it publishes nothing, and a message claiming otherwise would mislead anyone reading the channel.
Failure is unchanged.
Testing
actionlintclean,npm test58/58. The rendered payload was checked as valid JSON — the message interpolatessteps.pre.outputs.versionand.base, both already emitted by the derive step.Not testable before merge: the job only runs on
pushtomain, so the next merge is the real test.