-
Notifications
You must be signed in to change notification settings - Fork 271
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
fix(deps): update cargo pre-1.0 packages (minor) #702
Closed
Closed
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
@renovate[bot] your pull request is missing a changelog! |
renovate
bot
changed the title
fix(deps): update rust crate zip to 0.6
fix(deps): update cargo pre-1.0 packages (minor)
Mar 23, 2022
renovate
bot
force-pushed
the
renovate/cargo-all-pre-1.0
branch
from
March 23, 2022 14:18
d39f148
to
62a6773
Compare
✅ Deploy Preview for apollo-router-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
renovate
bot
force-pushed
the
renovate/cargo-all-pre-1.0
branch
4 times, most recently
from
April 4, 2022 21:33
8d202ee
to
715e514
Compare
renovate
bot
force-pushed
the
renovate/cargo-all-pre-1.0
branch
6 times, most recently
from
April 11, 2022 16:39
c6d533f
to
dcb4c2d
Compare
renovate
bot
force-pushed
the
renovate/cargo-all-pre-1.0
branch
4 times, most recently
from
April 14, 2022 17:27
e0000e3
to
420dbda
Compare
renovate
bot
force-pushed
the
renovate/cargo-all-pre-1.0
branch
7 times, most recently
from
April 28, 2022 15:02
728fc00
to
e6a473e
Compare
renovate
bot
force-pushed
the
renovate/cargo-all-pre-1.0
branch
5 times, most recently
from
May 3, 2022 10:59
0b4ef19
to
2914556
Compare
renovate
bot
force-pushed
the
renovate/cargo-all-pre-1.0
branch
9 times, most recently
from
January 24, 2023 15:23
a5fe555
to
dc3a346
Compare
renovate
bot
force-pushed
the
renovate/cargo-all-pre-1.0
branch
7 times, most recently
from
January 31, 2023 14:06
7a9004c
to
a4f0fb6
Compare
renovate
bot
force-pushed
the
renovate/cargo-all-pre-1.0
branch
4 times, most recently
from
February 7, 2023 15:03
499fd04
to
16d2d78
Compare
@renovate[bot], please consider creating a changeset entry in |
renovate
bot
force-pushed
the
renovate/cargo-all-pre-1.0
branch
2 times, most recently
from
February 8, 2023 00:00
9fb9c04
to
9b9e339
Compare
renovate
bot
force-pushed
the
renovate/cargo-all-pre-1.0
branch
3 times, most recently
from
February 21, 2023 15:38
9a5c5d0
to
898b84a
Compare
renovate
bot
force-pushed
the
renovate/cargo-all-pre-1.0
branch
from
February 21, 2023 21:29
898b84a
to
81dd411
Compare
Idk. This PR seems out of control. I'm going to close it and let it re-open. |
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.
This PR contains the following updates:
0.4.1
->0.5.0
0.4.1
->0.5.0
0.20
->0.21
0.11.0
->0.12.0
0.8.1
->0.9.0
0.2.2
->0.3.0
0.21.7
->0.22.3
0.8.26
->0.9.17
0.5.11
->0.7.2
Release Notes
apollographql/apollo-rs
v0.5.0
Compare Source
Features
ast::Definition
methods - goto-bus-stop, pull/456When working with
Definition
nodes, you can use the.name()
method to get the name of a definition, regardless of its kind. Forschema
definitions, it returnsNone
.You can use
.is_extension_definition()
to check if a definition node is an extension.Fixes
fix token order around type names - goto-bus-stop, issue/362, pull/443
Previously, the whitespace and comment around the
Int
type name would end up before the type name in the parse tree. This would mess up the location information for theInt
type name. Now this is fixed.fix spans after parsing unexpected tokens - goto-bus-stop, issue/325, pull/446
Location information for all nodes after an unexpected token was incorrect. It's better now, though still imperfect: lexing errors still have this problem.
fix ignored token positioning in the AST - goto-bus-stop, pull/445
This makes spans for all nodes more specific, not including ignored tokens after the node. When ignored tokens are consumed, they are first stored separately, and then added to the AST just before the next node is started. This way ignored tokens are always inside the outermost possible node, and therefore all individual nodes will have spans that only contain that node and not more.
The most obvious effect of this is that diagnostics now point to the exact thing they are about, instead of a bunch of whitespace :)
marshallpierce/rust-base64
v0.21.0
Compare Source
Migration
Functions
encode()
engine::general_purpose::STANDARD.encode()
orprelude::BASE64_STANDARD.encode()
encode_config()
engine.encode()
encode_config_buf()
engine.encode_string()
encode_config_slice()
engine.encode_slice()
decode()
engine::general_purpose::STANDARD.decode()
orprelude::BASE64_STANDARD.decode()
decode_config()
engine.decode()
decode_config_buf()
engine.decode_vec()
decode_config_slice()
engine.decode_slice()
The short-lived 0.20 functions were the 0.13 functions with
config
replaced withengine
.Padding
If applicable, use the preset engines
engine::STANDARD
,engine::STANDARD_NO_PAD
,engine::URL_SAFE
,or
engine::URL_SAFE_NO_PAD
.The
NO_PAD
ones require that padding is absent when decoding, and the others require thatcanonical padding is present .
If you need the < 0.20 behavior that did not care about padding, or want to recreate < 0.20.0's predefined
Config
sprecisely, see the following table.
encode_padding
decode_padding_mode
graphql-rust/graphql-client
v0.12.0
skip_none
andskip_serializing_none
jeromefroe/lru-rs
v0.9.0
Compare Source
LruCache.map
to hold a pointer, rather than ownedLruEntry
.redis-rs/redis-rs
v0.22.3
: v0.22.3Compare Source
0.22.3 (2023-01-23)
Fixes regression in 0.22.2 related to removed
ClusterConnection::check_connection
method. Thanks to @robjtede for identifying and fixing!Changes
ClusterConnection::check_connection()
method (#758 @robjtede)v0.22.2
: v0.22.2Compare Source
0.22.2 (2023-01-07)
This release adds various incremental improvements and fixes a few long-standing bugs. Thanks to all our
contributors for making this release happen.
Features
MGET
command (#729 @vamshiaruru-virgodesigns)Bug fixes
get
responses (#507 @hank121314)Changes
v0.22.1
: v0.22.1Compare Source
0.22.1 (2022-10-18)
Changes
v0.22.0
: v0.22.0Compare Source
Redis-rs is a high level redis library for Rust and aims to provide
convenient access to all Redis functionality through a very flexible
but low-level API. The crate has recently come under maintainership
by @djc and @jaymell. Much appreciation and many thanks to @mitsuhiko,
@badboy, @Marwes for their work in building this library over the years! The
new maintainers hope to improve the velocity of bug fixes, new features, and
PR reviews in the coming months.
This release adds various incremental improvements, including
additional convenience commands, improved Cluster APIs, and various other bug
fixes/library improvements.
Although the changes here are incremental, this is a major release due to the
breaking changes listed below.
This release would not be possible without our many wonderful
contributors -- thank you!
Breaking changes
sha1
feature (#576)Features
ahash
feature for using ahash internally & for redis values (#636 @utkarshgupta137)Changes
dtolnay/serde-yaml
v0.9.17
Compare Source
v0.9.16
Compare Source
-Zrustdoc-scrape-examples
on docs.rs for nowv0.9.15
Compare Source
v0.9.14
Compare Source
Deserializer
forTaggedValue
and&TaggedValue
(#339)v0.9.13
Compare Source
True
,TRUE
,False
,FALSE
as booleans,Null
,NULL
as null (#330)v0.9.12
Compare Source
Support deserializing tagged literal scalar into primitive (#327)
v0.9.11
Compare Source
v0.9.10
Compare Source
Display
forNumber
produce the same representation as serializing (#316)v0.9.9
Compare Source
v0.9.8
Compare Source
TaggedValue
when used withto_value
(#313)v0.9.7
Compare Source
v0.9.6
Compare Source
v0.9.5
Compare Source
Display
trait forserde_yaml::value::Tag
(#307, thanks @masinc)v0.9.4
Compare Source
serde_yaml::with::singleton_map
for serialization of enums as a 1-entry map (#300)Mapping
orValue
(#301)v0.9.3
Compare Source
v0.9.2
Compare Source
Debug
representation ofserde_yaml::Error
v0.9.1
Compare Source
v0.9.0
Compare Source
API documentation: https://docs.rs/serde_yaml/0.9
Highlights
The
serde_yaml::Value
enum gains aTagged
variant which represents the deserialization of YAML's!Tag
syntax. Tagged scalars, sequences, and mappings are all supported.An empty YAML input (or document containing only comments) will deserialize successfully to an empty map, empty sequence, or Serde struct as long as the struct has only optional fields. Previously this would error.
A new
.apply_merge()
method onValue
implements YAML's<<
merge key convention.The
Debug
representation ofserde_yaml::Value
has gotten vastly better (https://github.com/dtolnay/serde-yaml/pull/287).Deserialization of borrowed strings now works.
Value
's andMapping
's methodsget
andget_mut
have been generalized to support a &str argument, as opposed to requiring you to allocate and construct aValue::String
for indexing into another existingValue
.Mapping
exposes more APIs that have become conventional on map data structures, such as.keys()
,.values()
,.into_keys()
,.into_values()
,.values_mut()
, and.retain(|k, v| …)
.Breaking changes
Serialization no longer produces leading
---\n
on the serialized output. You can prepend this yourself if your use case demands it.Serialization of enum variants is now based on YAML's
!Tag
syntax, rather than JSON-style singleton maps.A bunch of non-base-10 edge cases in number parsing have been resolved. For example
0x+1
and++0x1
are now parsed as strings, whereas they used to be incorrectly treated as numbers.Deserializers obtained through iteration can no longer be iterated further:
The abandoned yaml-rust crate is no longer used as the YAML backend. The new libyaml-based backend surely has different edge cases and quirks than yaml-rust.
Some excessive
PartialEq
impls have been eliminated.The
serde_yaml::to_vec
function has been removed. Useserde_yaml::to_writer
for doing I/O, or useserde_yaml::to_string
+.into_bytes()
on the resulting String.The
serde_yaml::seed
module has been removed. Now that aserde_yaml::Deserializer
is publicly available, the same use cases can be addressed viaseed.deserialize(Deserializer::from_str(…))
instead.Bugfixes
Empty values in a mapping are supported, and deserialize to empty string when the corresponding struct field is of type string. Previously they would deserialize to "~" which makes no sense.
128-bit integer deserialization now supports hex and octal input.
Serde_yaml now includes a mitigation against a "billion laughs" attack in which malicious input involving YAML anchors and aliases is used to consume an amount of processing or memory that is exponential in the size of the input document. Serde_yaml will quickly produce an error in this situation instead.
toml-rs/toml
v0.7.2
Compare Source
v0.7.1
Compare Source
v0.7.0
Compare Source
v0.6.0
Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.