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

Upgrade from v1.2 to v1.3 #87

Merged

Conversation

svyatonik
Copy link
Contributor

@svyatonik svyatonik commented Nov 13, 2023

Opening PR mostly for visibility - I expect #56 to be finished before, which would bump everything to v1.2 and then I'll convert this PR to v1.2 -> v1.3. In its current state, this PR does v1.0 -> v1.3 bump, although I've only been looking at v1.2 -> v1.3 changelog, so everything else just compiles.

TODOs left in this PR (which I'd like to address after #56 is finished):

@liamaharon Can you, please, confirm that the paritytech/polkadot-sdk#1344 was necessary only for sdk CI fixes - that PR caught my eye when I was looking at 1.3 CHANGELOG and I was wondering if we need to do the same for Polkadot, Kusama and system parachains?

svyatonik and others added 30 commits November 3, 2023 11:38
[requires migration. onchain or offchain?]
[have no idea - Polkadot, Kusama, ...?]
adapt paritytech/polkadot-sdk#1234 (UMP price for delivery + benchmarks compilation)
@gavofyork gavofyork enabled auto-merge (squash) November 28, 2023 17:35
@acatangiu
Copy link
Contributor

Looks like review-bot is drunk on this PR 😆 still asking for 1 more review when there are already like 8 approves already with several L3+

@svyatonik maybe a rebase to re-trigger the bot check? or anyone with access to rebase from GH PR GUI.

Co-authored-by: Branislav Kontur <bkontur@gmail.com>
auto-merge was automatically disabled November 29, 2023 09:48

Head branch was pushed to by a user without write access

svyatonik and others added 3 commits November 29, 2023 12:48
Co-authored-by: Branislav Kontur <bkontur@gmail.com>
Co-authored-by: Branislav Kontur <bkontur@gmail.com>
Co-authored-by: Branislav Kontur <bkontur@gmail.com>
@svyatonik
Copy link
Contributor Author

Looks like review-bot is drunk on this PR 😆 still asking for 1 more review when there are already like 8 approves already with several L3+

@svyatonik maybe a rebase to re-trigger the bot check? or anyone with access to rebase from GH PR GUI.

@acatangiu Pushed some commits - still required :/

@svyatonik
Copy link
Contributor Author

Maybe that's the reason: #87 (comment). So if anything is pushed, then we need reviews again maybe?

@Bullrich
Copy link
Contributor

Looks like review-bot is drunk on this PR 😆 still asking for 1 more review when there are already like 8 approves already with several L3+
@svyatonik maybe a rebase to re-trigger the bot check? or anyone with access to rebase from GH PR GUI.

@acatangiu Pushed some commits - still required :/

I'm currently investigating this. It is weird, it doesn't get all the reviews and I'm not sure on why 🤔.

It is only getting 4 reviews ["acatangiu","bkchr","liamaharon","ggwpez"]. I'm looking into the logs for more detail.

@Bullrich
Copy link
Contributor

For some reason the API is not registering most of the reviews.

You can try it in your own terminal gh api /repos/polkadot-fellows/runtimes/pulls/87/reviews.

This returns a JSON which

Looks like review-bot is drunk on this PR 😆 still asking for 1 more review when there are already like 8 approves already with several L3+
@svyatonik maybe a rebase to re-trigger the bot check? or anyone with access to rebase from GH PR GUI.

@acatangiu Pushed some commits - still required :/

I'm currently investigating this. It is weird, it doesn't get all the reviews and I'm not sure on why 🤔.

It is only getting 4 reviews ["acatangiu","bkchr","liamaharon","ggwpez"]. I'm looking into the logs for more detail.

I found the issue.

It is a problem with pagination. The api returns the first 30 reviews, and there are more than that in this PR (comments & request for change also count).

I created paritytech/review-bot#102 to fix it. It will be my priority.

@acatangiu
Copy link
Contributor

@fellows please review and merge #105 to fix the CI.

@svyatonik
Copy link
Contributor Author

/merge

@fellowship-merge-bot fellowship-merge-bot bot merged commit 4e4da08 into polkadot-fellows:main Nov 30, 2023
13 checks passed
@fellowship-merge-bot
Copy link
Contributor

Enabled auto-merge in Pull Request

Available commands
  • /merge: Enables auto-merge for Pull Request
  • /merge cancel: Cancels auto-merge for Pull Request
  • /merge help: Shows this menu

For more information see the documentation

acatangiu pushed a commit to paritytech/polkadot-sdk that referenced this pull request Dec 6, 2023
…vel (#2422)

As suggested in this thread:
polkadot-fellows/runtimes#87 (comment)

We already have the `IsChildSystemParachain`, which may be used at relay
chain, but it can't be used at a parachain level. So let's use
`AllSiblingSystemParachains` for that. I was thinking about
`AllSystemParachains`, but it may cause wrong impression that it can be
used at a relay chain level.

---------

Co-authored-by: joe petrowski <25483142+joepetrowski@users.noreply.github.com>
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.

None yet