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

[0.1.x] update to pyodide 0.24.1 #67

Merged
merged 1 commit into from
Sep 26, 2023

Conversation

bollwyvl
Copy link
Contributor

@bollwyvl bollwyvl commented Sep 26, 2023

References

Changes

  • update various pyodide versions to 0.24.1

@github-actions
Copy link
Contributor

lite-badge 👈 Try it on ReadTheDocs

@bollwyvl bollwyvl added the enhancement New feature or request label Sep 26, 2023
@bollwyvl bollwyvl marked this pull request as ready for review September 26, 2023 02:08
Copy link
Member

@jtpio jtpio left a comment

Choose a reason for hiding this comment

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

Thanks!

@jtpio jtpio merged commit 9eb0aef into jupyterlite:0.1.x Sep 26, 2023
12 of 13 checks passed
@jtpio
Copy link
Member

jtpio commented Sep 26, 2023

@meeseeksdev please backport to main

@lumberbot-app
Copy link

lumberbot-app bot commented Sep 26, 2023

Something went wrong ... Please have a look at my logs.

It seems that the branch you are trying to backport to does not exist.

@jtpio
Copy link
Member

jtpio commented Sep 26, 2023

@meeseeksdev please backport to main

@lumberbot-app
Copy link

lumberbot-app bot commented Sep 26, 2023

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

  1. Checkout backport branch and update it.
git checkout main
git pull
  1. Cherry pick the first parent branch of the this PR on top of the older branch:
git cherry-pick -x -m1 9eb0aef053eb549645d1a2d6988db271487e3a09
  1. You will likely have some merge/cherry-pick conflict here, fix them and commit:
git commit -am 'Backport PR #67: [0.1.x] update to pyodide 0.24.1'
  1. Push to a named branch:
git push YOURFORK main:auto-backport-of-pr-67-on-main
  1. Create a PR against branch main, I would have named this PR:

"Backport PR #67 on branch main ([0.1.x] update to pyodide 0.24.1)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants