Post Honeycomb release marker on release#2114
Merged
Merged
Conversation
colincasey
marked this pull request as ready for review
July 6, 2026 15:25
colincasey
requested review from
a team and
edmorley
and removed request for
a team and
edmorley
July 6, 2026 15:25
edmorley
approved these changes
Jul 6, 2026
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.
Passes the
HONEYCOMB_API_KEYsecret through to the shared_classic-buildpack-publish.yml@latestworkflow ashoneycomb_api_key, enabling a Honeycomb release marker on thebuildsdataset for each production publish of this classic buildpack.The shared workflow support landed in heroku/languages-github-actions#369 (released in
v1.11.0, which@latestnow resolves to), and this repo'sHONEYCOMB_API_KEYsecret is configured — so once this PR merges, the marker step posts to thebuildsdataset on each production publish. The step is a safe no-op in any context where the secret is absent — it is gated onenv.HONEYCOMB_API_KEY != '' && env.MODE == 'production'and declaredrequired: falsein the shared workflow.What
honeycomb_api_key: ${{ secrets.HONEYCOMB_API_KEY }}to thereleasejob'ssecrets:block, forwarding the repo secret to the shared workflow's optional input.The marker behavior (opt-in, production-only, idempotent, best-effort) lives in the shared workflow — see heroku/languages-github-actions#369 for details.
W-22846373