Skip to content

Release workflow update - #12241

Open
anakin87 wants to merge 4 commits into
mainfrom
release-workflow-update
Open

Release workflow update#12241
anakin87 wants to merge 4 commits into
mainfrom
release-workflow-update

Conversation

@anakin87

@anakin87 anakin87 commented Aug 4, 2026

Copy link
Copy Markdown
Member

Related Issues

Proposed Changes:

  • stop updating Platform repos manually, just invoke the trigger and wait for the created PRs
  • if we can't find the expected PR, do not mark the release as failed but report a warning on Slack

How did you test it?

Several local tests. Haven't tested the new release workflow with an actual release, so something might still fail next time; we'll fix it.

Notes for the reviewer

Once this is done, I'll see which changes to port into the v2.31.x branch (2.31 release line).

Checklist

  • I have read the contributors guidelines and the code of conduct.
  • I have updated the related issue with new insights and changes.
  • I have added unit tests and updated the docstrings.
  • I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test: and added ! in case the PR includes breaking changes.
  • I have documented my code.
  • I have added a release note file, following the contributors guidelines.
  • I have run pre-commit hooks and fixed any issue.

@vercel

vercel Bot commented Aug 4, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
haystack-docs Ignored Ignored Preview Aug 4, 2026 4:30pm

Request Review

@github-actions

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Coverage report

This PR does not seem to contain any modification to coverable code.

@anakin87
anakin87 marked this pull request as ready for review August 4, 2026 15:41
@anakin87
anakin87 requested a review from a team as a code owner August 4, 2026 15:41
@anakin87
anakin87 requested review from julian-risch and removed request for a team August 4, 2026 15:41
Move GH_TOKEN from the job-level env to just the four steps that
call gh, so the checkout and final failure-check steps in this job
no longer have the bot token in their environment.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

@julian-risch julian-risch left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Looks good to me! Thanks for working on this. The change that I applied directly is about scoping the token only to the steps that need it instead of the job, following best practices. Only other action in the job right now is actions/checkout but it's still better to scope it only to the steps that need it. Otherwise there is the risk that we might add another step to the job in future and increase exposure more and more. It's also better to follow this standard consistently throughout our repos.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants