search

sdttttt / gcr

📑 Compact specification git commit tool, it has a variety of practical small functions. (Inspired by git-cz on Node.js)
https://crates.io/crates/grc
The Unlicense
28 stars 6 forks source link

chore(deps): bump serde from 1.0.125 to 1.0.134 #92

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps serde from 1.0.125 to 1.0.134.

Release notes

Sourced from serde's releases.

v1.0.134

  • Improve error messages on deserializing NonZero integers from a 0 value (#2158)

v1.0.133

  • Optimize deserialization of data structures that contain recursive use of flatten fields or tag or untagged enums (#2148)

v1.0.132

  • Enable Serialize and Deserialize impls for std::sync::atomic::{AtomicI64, AtomicU64} on riscv64 arch (#2141, thanks @​Avimitin)

v1.0.131

  • Avoid unused_results being triggered in generated code for adjacently tagged enum (#2116, thanks @​tyranron)

v1.0.130

  • Provide MapAccess and SeqAccess impl for reference to a dynamically sized existing impl (#2081)

v1.0.129

  • Support deserialization of remote structs that used packed repr (#2078, #2079, #2080)

v1.0.128

v1.0.127

  • Resolve warning in rustc nightly-2021-07-31+ compiling serde_test

v1.0.126

  • Resolve conflict with forbid(future_incompatible) lint setting in generated code (#2026, thanks @​hyd-dev)
Commits
  • 3bb4a5a Release 1.0.134
  • 6164627 Merge pull request #2159 from serde-rs/nonzero
  • 51aaf49 Write better Visitor for NonZero integers
  • bc66aeb Add tests of deserializing NonZero
  • 7e7044d Ignore clippy in number conversion tests
  • 5498dc0 Add tests of num conversion errors
  • ff04e8b Improve coverage of num conversion in test suite
  • 69240c1 Eliminate macro from serialization tests
  • 237434f Accept ?Sized references in assert_ser_tokens
  • 1833914 Eliminate macro from deserialization error tests
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
pull-request-quantifier-deprecated[bot] commented 2 years ago

This PR has 10 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

Quantification details

``` Label : Extra Small Size : +5 -5 Percentile : 4% Total files changed: 2 Change summary by file extension: .lock : +4 -4 .toml : +1 -1 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detetcted. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

codecov[bot] commented 2 years ago

Codecov Report

Merging #92 (8e0c703) into master (e7754c8) will not change coverage. The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #92   +/-   ##
=======================================
  Coverage   49.75%   49.75%           
=======================================
  Files          11       11           
  Lines         623      623           
=======================================
  Hits          310      310           
  Misses        313      313

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update e7754c8...8e0c703. Read the comment docs.

dependabot[bot] commented 2 years ago

Superseded by #93.