[docs] Call render_release_notes.rb within docs #5491
Merged
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.
Describe the PR
While release, I've seen the following warnings:
The reason is, that we use in our toplevel Gemfile already liquid 5.x, but in docs/Gemfile we still use liquid 4.x. We also can't just update to liquid 5 everywhere, as jekyll still uses liquid 4.
Furthermore, the pmdtester uses liquid 5 already.
I've cleaned up a bit, how we call render_release_notes.rb, so that we call it within the docs directory. Then we can reuse the Gemfile from docs rather than using a group.
The toplevel Gemfile is then only used for Danger and pmdtester.
Related issues
Ready?
./mvnw clean verifypasses (checked automatically by github actions)