Repository navigation
feat(updates): tell admins and notification targets when a new release is out - #270
Merged
Merged
Conversation
…e is out Once per release: an email to every admin (updates.email, on by default) and a lens.release event for the namespaces' notification targets that choose it. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XturGhybJzfgZvbFxfNB2o
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
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 Adeel · project thread
Description
Before: a new Lens release showed up only in
GET /admin/updates, for an admin who looked.After: once per release, Lens emails every admin (
updates.email, on by default; needs an email server) and sends a newlens.releasenotification event to the webhooks, Matterbridge, Slack and Discord targets whose namespace owners choose it. The email links to Settings › Updates and backups.How:
updates.announce()runs after each check (the daily one andPOST /admin/updates/check), claimsapp_service:release-notice-<tag>so only one process tells anyone, then callsnotify.release()andemail.send_release_email().Motivation and Context
Adeel asked for upgrade notifications. This builds on #260. Docs:
docs/updates.md(Being told),docs/notifications.md(events).Types of changes
!in the title)Checklist:
make hookschecks it on commit).docs/accordingly.## UnreleasedinCHANGELOG.md.🤖 Generated with Claude Code
https://claude.ai/code/session_01XturGhybJzfgZvbFxfNB2o
Generated by Claude Code