chore: bump baseline to v0.16.1, add Telegram release notifications - #149
Merged
Conversation
v0.16.0 added notify-telegram-release-shared.yml, v0.16.1 fixed it to include release notes in the message. Wires it up the same way notify-telegram-pr.yml already does, reusing the existing TELEGRAM_BOT_TOKEN/TELEGRAM_CHAT_ID secrets. Also catches .pre-commit-config.yaml up - it was still pinned to v0.13.1 while every workflow file had already moved to v0.15.0. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
1 participant
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.
Summary
embedder.yml,github.yml,lint.yml,notify-telegram-pr.yml), and.pre-commit-config.yaml(was still stuck on v0.13.1, two versions behind the workflows)..github/workflows/notify-telegram-release.yml, using baseline v0.16.0's newnotify-telegram-release-shared.yml(v0.16.1 fixed it to include release notes in the message) - same patternnotify-telegram-pr.ymlalready uses, reusing the existingTELEGRAM_BOT_TOKEN/TELEGRAM_CHAT_IDsecrets, no new secrets needed.Test plan
deploy/tests/(48 tests) pass