Skip to content

Bump OpenJPH to 0.21.5 #2097

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

Merged

Conversation

palemieux
Copy link
Contributor

Closes #2096

@palemieux palemieux changed the title Bump OpenJPH to 0.21.4 Bump OpenJPH to 0.21.5 Aug 14, 2025
@palemieux palemieux force-pushed the issues/bump-openjph branch 3 times, most recently from 4bad5f5 to 27060e3 Compare August 14, 2025 04:15
@cary-ilm
Copy link
Member

Something has gone wrong with the python wheels, happening on all branches, unrelated to this PR. I'll track it down.

@Vertexwahn
Copy link
Contributor

+1 for Bazel-related changes ;)

@cary-ilm
Copy link
Member

@palemieux, if you can you rebase this off of the main branch, I'll merge it.

Normally, most PR's allow admins to push to the branch so I can do the update myself, but I think you have have things configured so that is not an option. Is that intentional? I usually see an "update" button next to "This branch is out-of-date", but I don't here. I think this comes from the "Allow edits and access to secrets by maintainers". Did you disable that?

Signed-off-by: Pierre-Anthony Lemieux <[email protected]>
@palemieux palemieux force-pushed the issues/bump-openjph branch from 27060e3 to a189071 Compare August 15, 2025 03:08
@cary-ilm cary-ilm merged commit 0afe0a2 into AcademySoftwareFoundation:main Aug 15, 2025
49 checks passed
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.

OpenJPH version should be bumped
3 participants