Update provider #26632
Merged
Update provider #26632
Conversation
This file contains 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
|
We can't remove packages, unfortunately -- there may be other opam repositories that depend on this ourside of ours. However, you can add a |
mbarbin
force-pushed
the
update-provider
branch
from
8778211 to
4756ca4
Compare
|
OK thanks for letting me know. I looked at the manual and discovered a wealth of options I wasn't aware of, such as ... a deprecated flag for releases with known bugs! Thanks, updated 😃 |
|
Looks perfect, thanks for the flexibility! |
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.
Add maintainer email to existing provider packages
Flagged older
provider.0.0.4as deprecated.This version has a bug in the binding lookup I'd be happy to forget.
opam.ocaml.orgsays this package is not usedso I propose to simply delete this release. Is that technically acceptable?