Repository navigation
feat(deploy): let the changelog job resolve Slack users via identity API [CPONETOPS-1176] - #362
Merged
morten-andersen merged 2 commits intoOct 6, 2026
Conversation
…API [CPONETOPS-1176] The release notification tags contributors with Slack mentions, but mapping a GitHub login to a Slack user relies on an internal, VPN-only identity service (the GitHub-profile-email fallback reaches very few people). In deploy-kotlin and deploy-kotlin-v2, pass the repo/org variable CHANGELOG_IDENTITY_RESOLVE_URL to changelog-cli-action. The URL is a variable rather than workflow code because this repo is public. When changelog-release-notify-channel, that variable and the new optional TAILSCALE_AUTHKEY secret are all set, the create-changelog job first joins the tailnet (same pinned tailscale/github-action and login server as the Kotlin PR workflow) and polls the service until it answers, since `tailscale up` returns before routes are usable. Both steps are continue-on-error: on any failure the CLI just falls back to its email lookups and the job still succeeds. Documented in workflow-guide.md and CLAUDE.md. Inert until the pinned changelog-cli release includes the identity resolver. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
cweinberger
approved these changes
Sep 30, 2026
…nties-to-mention-people
morten-andersen
deleted the
chore/CPONETOPS-1176/add-resolving-slack-identies-to-mention-people
branch
October 6, 2026 12:10
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 release notification tags contributors with Slack mentions, but mapping a GitHub login to a Slack user relies on an internal, VPN-only identity service (the GitHub-profile-email fallback reaches very few people).
In deploy-kotlin and deploy-kotlin-v2, pass the repo/org variable CHANGELOG_IDENTITY_RESOLVE_URL to changelog-cli-action. The URL is a variable rather than workflow code because this repo is public.
When changelog-release-notify-channel, that variable and the new optional TAILSCALE_AUTHKEY secret are all set, the create-changelog job first joins the tailnet (same pinned tailscale/github-action and login server as the Kotlin PR workflow) and polls the service until it answers, since
tailscale upreturns before routes are usable. Both steps are continue-on-error: on any failure the CLI just falls back to its email lookups and the job still succeeds.Depends on monta-app/changelog-cli-action#101