Skip to content

ci: automatically tag contributors in GitHub release notes#10074

Merged
anakin87 merged 3 commits intomainfrom
github-relnotes-add-contributors
Nov 13, 2025
Merged

ci: automatically tag contributors in GitHub release notes#10074
anakin87 merged 3 commits intomainfrom
github-relnotes-add-contributors

Conversation

@anakin87
Copy link
Copy Markdown
Member

@anakin87 anakin87 commented Nov 12, 2025

Related Issues

Proposed Changes:

  • Modify the GitHub release workflow to automatically tag contributors for minor releases (and their release candidates)
  • Other minor improvements

How did you test it?

Tested on #10073 (PR on the v2.20.x branch). Check out the debug step of this workflow run: https://github.com/deepset-ai/haystack/actions/runs/19302188326/job/55199499137

## 💙 Big thank you to everyone who contributed to this release!

@Amnah199, @anakin87, @cmnemoi, @davidsbatista, @dfokina, @HamidOna, @Hansehart, @jdb78, @sjrl, @swapniel99, @TaMaN2031A, @tstadel, @vblagoje

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
Copy link
Copy Markdown

vercel Bot commented Nov 12, 2025

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

1 Skipped Deployment
Project Deployment Preview Comments Updated (UTC)
haystack-docs Ignored Ignored Preview Nov 13, 2025 1:39pm

@anakin87 anakin87 changed the title GitHub relnotes add contributors ci: automatically tag contributors in GitHub release notes Nov 12, 2025
@anakin87 anakin87 force-pushed the github-relnotes-add-contributors branch from 43a4489 to 80bddcb Compare November 12, 2025 15:23
uses: docker://pandoc/core:3.8
with:
args: "--from rst --to markdown_github --no-highlight relnotes.rst -o relnotes.md --wrap=none"
args: "--from rst --to gfm --syntax-highlighting=none --wrap=none relnotes.rst -o relnotes.md"
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

some arguments were deprecated

bodyFile: "relnotes.md"
prerelease: ${{ steps.version.outputs.current_pre_release }}
bodyFile: "enhanced_relnotes.md"
prerelease: ${{ steps.version.outputs.current_pre_release != '' }}
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

prerelease should be a boolean. The current approach was not working to set a version as pre-release.

@anakin87 anakin87 marked this pull request as ready for review November 12, 2025 15:29
@anakin87 anakin87 requested a review from a team as a code owner November 12, 2025 15:29
@anakin87 anakin87 requested review from mpangrazzi and vblagoje and removed request for a team November 12, 2025 15:29
Copy link
Copy Markdown
Contributor

@mpangrazzi mpangrazzi left a comment

Choose a reason for hiding this comment

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

Looks good! Left two minor comments.

Comment thread .github/workflows/github_release.yml
uses: docker://pandoc/core:3.8
with:
args: "--from rst --to markdown_github --no-highlight relnotes.rst -o relnotes.md --wrap=none"
args: "--from rst --to gfm --syntax-highlighting=none --wrap=none relnotes.rst -o relnotes.md"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Here we can also do something like:

"--from rst --to gfm --syntax-highlighting=none --wrap=none relnotes.rst -o enhanced_relnotes.md"

to save the copy step below. Your choice!

Copy link
Copy Markdown
Member Author

@anakin87 anakin87 Nov 13, 2025

Choose a reason for hiding this comment

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

Ah, unfortunately pandoc creates a markdown files that cannot be later modified (wrong permissions).
I also tried to run chmod and I got other permission issues. I am creating the copy for this reason.
If you have better ideas, feel free to share.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

ok, let's then leave things as is (since it's working). I would add a comment about that, maybe next time we could try to investigate better.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Makes sense. Comment added in 719219a

@anakin87 anakin87 requested a review from mpangrazzi November 13, 2025 11:33
uses: docker://pandoc/core:3.8
with:
args: "--from rst --to markdown_github --no-highlight relnotes.rst -o relnotes.md --wrap=none"
args: "--from rst --to gfm --syntax-highlighting=none --wrap=none relnotes.rst -o relnotes.md"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

ok, let's then leave things as is (since it's working). I would add a comment about that, maybe next time we could try to investigate better.

@vblagoje
Copy link
Copy Markdown
Member

I didn't even know we have this generate notes action, I thought we were supposed to do this step manually?!

@anakin87
Copy link
Copy Markdown
Member Author

I didn't even know we have this generate notes action, I thought we were supposed to do this step manually?!

Release notes are automatically generated but contributors were manually added and tagged.
In this PR, I am adding a step to automatically do this, in the perspective of release automation.

@anakin87 anakin87 merged commit e57b225 into main Nov 13, 2025
11 checks passed
@anakin87 anakin87 deleted the github-relnotes-add-contributors branch November 13, 2025 13:42
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.

Automate tagging contributors in release notes

3 participants