Bump av-metrics-decoders in other av-metrics crates #298
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
|
New clippy errors. I opened #299 to fix those. |
FreezyLemon
force-pushed
the
bump-decoder
branch
2 times, most recently
from
ce24702
to
331fab0
Compare
FreezyLemon
force-pushed
the
bump-decoder
branch
from
331fab0
to
13efa8a
Compare
|
Looks like the other crates finally build again 🎉 |
FreezyLemon
force-pushed
the
bump-decoder
branch
from
13efa8a
to
fdea5d3
Compare
FreezyLemon
force-pushed
the
bump-decoder
branch
from
fdea5d3
to
93e7f39
Compare
FreezyLemon
force-pushed
the
bump-decoder
branch
from
c1d8def
to
584d107
Compare
|
The history has gotten a bit mangled here. Basically, I updated After this, both -decoders and -tool need a new crates.io release. I don't have the permissions for these packages. |
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.
These are breaking changes1 because the
Y4MDecodertype is exposed in the API (and got changed inav-metrics-decoders). The changes are pretty simple otherwise. I wanted to update some dependencies, but this should be done first I thinkFootnotes
Nevermind. The tests project is obviously not published/versioned and I'm not sure what compatibility guarantees the
av-metrics-toolis supposed to make. ↩