Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Github workflow to automate release draft creation #3978

Merged

Conversation

EgorPopelyaev
Copy link
Contributor

This PR introduces the github flow which will create a release draft automatically when the rc tag is pushed. The flow contains the following steps:

  • Gets the info about rust version used to build the node
  • Builds the runtimes using srtool
  • Extracts the info about each runtime
  • Aggregates the changelog from the prdocs
  • Creates the release draft containing all the info related to the release (changelog, runtimes, rust versions)
  • Attaches the runtimes to the draft
  • Posts the message to the RelEng internal channel to inform that the build is done.

Related to the #3295

@paritytech-review-bot paritytech-review-bot bot requested a review from a team April 4, 2024 10:23
.github/scripts/common/lib.sh Outdated Show resolved Hide resolved
.github/workflows/release-30_publish_release_draft.yml Outdated Show resolved Hide resolved
@paritytech-review-bot paritytech-review-bot bot requested a review from a team April 8, 2024 10:01
Copy link
Member

@ggwpez ggwpez left a comment

Choose a reason for hiding this comment

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

Fantastic 🚀 💯

.github/workflows/release-30_publish_release_draft.yml Outdated Show resolved Hide resolved
.github/workflows/release-30_publish_release_draft.yml Outdated Show resolved Hide resolved
prdoc/1.9.0/pr_3513.prdoc Outdated Show resolved Hide resolved
scripts/release/build-changelogs.sh Outdated Show resolved Hide resolved
@EgorPopelyaev EgorPopelyaev added this pull request to the merge queue Apr 8, 2024
@ggwpez ggwpez removed this pull request from the merge queue due to a manual request Apr 8, 2024
EgorPopelyaev and others added 4 commits April 8, 2024 14:13
Co-authored-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
Co-authored-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
@EgorPopelyaev EgorPopelyaev added this pull request to the merge queue Apr 8, 2024
Merged via the queue into paritytech:master with commit 216509d Apr 8, 2024
130 of 136 checks passed
@EgorPopelyaev EgorPopelyaev deleted the ep-automate-release-notes branch April 8, 2024 14:11
Ank4n pushed a commit that referenced this pull request Apr 9, 2024
This PR introduces the github flow which will create a release draft
automatically when the rc tag is pushed. The flow contains the following
steps:

- Gets the info about rust version used to build the node
- Builds the runtimes using `srtool`
- Extracts the info about each runtime 
- Aggregates the changelog from the prdocs
- Creates the release draft containing all the info related to the
release (changelog, runtimes, rust versions)
- Attaches the runtimes to the draft
- Posts the message to the RelEng internal channel to inform that the
build is done.

Related to the #3295

---------

Co-authored-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
dharjeezy pushed a commit to dharjeezy/polkadot-sdk that referenced this pull request Apr 9, 2024
This PR introduces the github flow which will create a release draft
automatically when the rc tag is pushed. The flow contains the following
steps:

- Gets the info about rust version used to build the node
- Builds the runtimes using `srtool`
- Extracts the info about each runtime 
- Aggregates the changelog from the prdocs
- Creates the release draft containing all the info related to the
release (changelog, runtimes, rust versions)
- Attaches the runtimes to the draft
- Posts the message to the RelEng internal channel to inform that the
build is done.

Related to the paritytech#3295

---------

Co-authored-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
R0-silent Changes should not be mentioned in any release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants