Release 4.3.0#269
Merged
Merged
Conversation
* CHANGES: cut the 4.3.0 section (js_of_ocaml >= 6.4.0 fix + lwt_ppx). * CI: refresh the dune 3.23.1 pin rationale now that #267 requires js_of_ocaml >= 6.4.0 (the wasm runtime bug persists on 6.4.0; fixed only in the not-yet-released 6.4.1).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release 4.3.0, cut to ship the js_of_ocaml 6.4 build fix (#267).
Changes since 4.2.0
inputElement##.files), merged in Ot_picture_uploader: fix build with js_of_ocaml >= 6.4.0 #267.js_of_ocaml >= 6.4.0is now required.This PR
CHANGES: turn theunreleasedsection into4.3.0 (2026-07-02)and note the jsoo requirement bump + lwt_ppx.js_of_ocaml < 6.4cap but left the dune-pin comments inbuild.yml/doc.ymldescribing the old '6.3.x / capped below 6.4' rationale. Refresh them: thedune 3.23.1pin is still needed (the wasm runtime bug persists on 6.4.0, fixed only in the not-yet-released 6.4.1), but the justification now reflects>= 6.4.0. No command change.The tag is pushed after merge, then the package is published to opam.