Skip to content

[WT-1042] GHA release trigger fine-tuning#17141

Merged
stevejalim merged 4 commits intomainfrom
WT-1042--gha-release-trigger--amends
Apr 17, 2026
Merged

[WT-1042] GHA release trigger fine-tuning#17141
stevejalim merged 4 commits intomainfrom
WT-1042--gha-release-trigger--amends

Conversation

@stevejalim
Copy link
Copy Markdown
Contributor

If this changeset needs to go into the FXC codebase, please add the WMO and FXC label.

One-line summary

Significant changes and points to review

Issue / Bugzilla link

Testing

Include the git log --oneline output (origin/prod..HEAD) in the
#www Slack notification, not just the count.
GitHub does not fire push-triggered workflows when the push is made
using GITHUB_TOKEN. Using a PAT (BEDROCK_GHA_RELEASE_WORKFLOW_PAT)
means the push is attributed to a real user and build-and-push.yml
fires as expected.
@stevejalim stevejalim force-pushed the WT-1042--gha-release-trigger--amends branch from c7f6493 to 2f16680 Compare April 17, 2026 13:49
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Bedrock GitHub Actions release workflow to improve release notifications and ensure downstream workflows are triggered when pushing stage/prod refs.

Changes:

  • Include a commit log summary in the initial Slack “release started” message.
  • Add PAT-based authentication to actions/checkout in stage/prod deploy jobs so branch/tag pushes trigger downstream workflows.

Comment thread .github/workflows/release.yml Outdated
Comment thread .github/workflows/release.yml Outdated
Comment thread .github/workflows/release.yml Outdated
- Use jq to properly JSON-encode the commit log so commit subjects
  containing quotes or backslashes don't break the Slack payload
- Truncate raw log before encoding to avoid splitting escape sequences
- Use printf instead of echo for predictable backslash handling
@stevejalim stevejalim changed the title Wt 1042 gha release trigger amends [WT-1042] GHA release trigger fine-tuning Apr 17, 2026
@stevejalim stevejalim requested a review from Copilot April 17, 2026 14:41
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR refines the release GitHub Actions workflow by improving Slack notifications with a commit list and ensuring release branch/tag pushes correctly trigger downstream workflows (e.g., build-and-push.yml).

Changes:

  • Capture and include the pending commit log in the “starting release” Slack message, with escaping intended to make it safe for Slack’s Block Kit JSON payload.
  • Add a fallback commit_log output when origin/prod is unavailable.
  • Switch actions/checkout to use a PAT for the stage/prod deploy jobs so pushes trigger downstream workflow runs.

Comment thread .github/workflows/release.yml Outdated
Comment on lines +76 to +78
# otherwise break the JSON. Truncate the raw log before encoding to avoid
# splitting escape sequences, leaving headroom for Slack's 3000-char block limit
# after the prefix text the Slack action prepends.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
@stevejalim stevejalim merged commit fb19769 into main Apr 17, 2026
3 checks passed
@stevejalim stevejalim deleted the WT-1042--gha-release-trigger--amends branch April 17, 2026 14:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants