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

chore: add manual trigger for Polkadot releases dependencies #463

Merged
merged 4 commits into from
Feb 22, 2023

Conversation

ntn-x2
Copy link
Member

@ntn-x2 ntn-x2 commented Feb 16, 2023

Fixes https://github.com/KILTprotocol/ticket/issues/2403.

I was playing around with subalfred and found out this nice feature, which we might want to integrate into our update flow. The action is configured to be run manually by providing the versions we are updating from and to.

There is one thing that would break if we keep changing the weekly board project name to include the sprint goal, I think we could start tracking that separately. -> replaced project-name with project-number, thanks @ggera

What do you guys think? Would it make sense?

@ntn-x2 ntn-x2 self-assigned this Feb 16, 2023
@ggera
Copy link
Member

ggera commented Feb 16, 2023

Fixes KILTprotocol/ticket#2403.

I was playing around with subalfred and found out this nice feature, which we might want to integrate into our update flow. The action is configured to be run manually by providing the versions we are updating from and to.

There is one thing that would break if we keep changing the weekly board project name to include the sprint goal, I think we could start tracking that separately.

What do you guys think? Would it make sense?

Looks awesome,, can we take a learning from ticket-version-bump and if possible put both in a single repo?

1 similar comment
@ggera
Copy link
Member

ggera commented Feb 16, 2023

Fixes KILTprotocol/ticket#2403.

I was playing around with subalfred and found out this nice feature, which we might want to integrate into our update flow. The action is configured to be run manually by providing the versions we are updating from and to.

There is one thing that would break if we keep changing the weekly board project name to include the sprint goal, I think we could start tracking that separately.

What do you guys think? Would it make sense?

Looks awesome,, can we take a learning from ticket-version-bump and if possible put both in a single repo?

.github/workflows/polkadot-release-list.yml Outdated Show resolved Hide resolved
@ntn-x2
Copy link
Member Author

ntn-x2 commented Feb 16, 2023

There you go! I remember we had an action somewhere for this sort of ticket, but I could not find it!

Do you think it should live in the ticket repo or in the node repo? I personally think it should live in the node repo, which is also easier to access for most people.
Thanks for the suggestion, that's exactly what I was looking for!

@ntn-x2
Copy link
Member Author

ntn-x2 commented Feb 21, 2023

Since there's a new Polkadot 0.9.38 release, what do you think about reviewing this PR and test it with the new release? @weichweich @trusch

@ntn-x2 ntn-x2 merged commit 29e9c2b into develop Feb 22, 2023
@ntn-x2 ntn-x2 deleted the aa/subalfred-releases branch February 22, 2023 12:35
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.

3 participants