Remove capnp-rpc-lwt compatibility package#314
Merged
talex5 merged 1 commit intomirage:masterfrom Feb 3, 2025
Merged
Conversation
This shouldn't need any future releases; no point releasing an unchanged version every time there's a capnp-rpc release.
talex5
added a commit
to talex5/opam-repository
that referenced
this pull request
Feb 4, 2025
CHANGES: - Update to mirage-crypto-rng 1.2.0 (@talex5 mirage/capnp-rpc#313). There is no need to do `Mirage_crypto_rng_eio.run` now. - `Restorer.Table.create` now takes a switch (@talex5 mirage/capnp-rpc#306). The table is now cleared when the switch finishes. Avoids having to remember to set this up manually. - Update README now that 2.0 is released (@talex5 mirage/capnp-rpc#307 mirage/capnp-rpc#308). Build and opam metadata: - OCaml 5.2 is the minimum version (@talex5 mirage/capnp-rpc#305). - Update Windows CI (@smorimoto mirage/capnp-rpc#310 mirage/capnp-rpc#311). - Add `x-maintenance-intent` to opam files (@talex5 mirage/capnp-rpc#315, requested by @hannesm). - Remove capnp-rpc-lwt compatibility package (@talex5 mirage/capnp-rpc#314). The existing release should continue working; no point releasing an unchanged version every time there's a capnp-rpc release.
talex5
added a commit
to talex5/opam-repository
that referenced
this pull request
Feb 4, 2025
CHANGES: - Update to mirage-crypto-rng 1.2.0 (@talex5 mirage/capnp-rpc#313). There is no need to do `Mirage_crypto_rng_eio.run` now. - `Restorer.Table.create` now takes a switch (@talex5 mirage/capnp-rpc#306). The table is now cleared when the switch finishes. Avoids having to remember to set this up manually. - Update README now that 2.0 is released (@talex5 mirage/capnp-rpc#307 mirage/capnp-rpc#308). Build and opam metadata: - OCaml 5.2 is the minimum version (@talex5 mirage/capnp-rpc#305). - Update Windows CI (@smorimoto mirage/capnp-rpc#310 mirage/capnp-rpc#311). - Add `x-maintenance-intent` to opam files (@talex5 mirage/capnp-rpc#315, requested by @hannesm). - Remove capnp-rpc-lwt compatibility package (@talex5 mirage/capnp-rpc#314). The existing release should continue working; no point releasing an unchanged version every time there's a capnp-rpc release.
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
1 participant
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.
This shouldn't need any future releases; no point releasing an unchanged version every time there's a capnp-rpc release.