codecov[bot]
commented
5 years ago Codecov Report
Merging #75 into master will not change coverage. The diff coverage is
n/a.
@@ Coverage Diff @@
## master #75 +/- ##
=======================================
Coverage 95.54% 95.54%
=======================================
Files 12 12
Lines 516 516
=======================================
Hits 493 493
Misses 23 23
Bumps grpcio from 1.24.0 to 1.24.1.
Release notes
*Sourced from [grpcio's releases](https://github.com/grpc/grpc/releases).* > ## Release v1.24.1 > This is the 1.24.1 release ([ganges](https://github.com/grpc/grpc/blob/master/doc/g_stands_for.md)) of gRPC Core. > > Please see the notes for the previous releases here: https://github.com/grpc/grpc/releases. Please consult https://grpc.io/ for all information regarding this product. > > This release contains refinements, improvements, and bug fixes.Changelog
*Sourced from [grpcio's changelog](https://github.com/grpc/grpc/blob/master/doc/grpc_release_schedule.md).* > # gRPC Release Schedule > > Below is the release schedule for gRPC [Java](https://github.com/grpc/grpc-java/releases), [Go](https://github.com/grpc/grpc-go/releases) and [Core](https://github.com/grpc/grpc/releases) and its dependent languages C++, C#, Objective-C, PHP, Python and Ruby. > > Releases are scheduled every six weeks on Tuesdays on a best effort basis. In some unavoidable situations a release may be delayed or a language may skip a release altogether and do the next release to catch up with other languages. See the past releases in the links above. A six-week cycle gives us a good balance between delivering new features/fixes quickly and keeping the release overhead low. > > Releases are cut from release branches. For Core and Java repos, the release branch is cut two weeks before the scheduled release date. For Go, the branch is cut just before the release. An RC (release candidate) is published for Core and its dependent languages just after the branch cut. This RC is later promoted to release version if no further changes are made to the release branch. We do our best to keep head of master branch stable at all times regardless of release schedule. Daily build packages from master branch for C#, PHP, Python, Ruby and Protoc plugins are published on [packages.grpc.io](https://packages.grpc.io/). If you depend on gRPC in production we recommend to set up your CI system to test the RCs and, if possible, the daily builds. > > Names of gRPC releases are [here](https://github.com/grpc/grpc/blob/master/doc/g_stands_for.md). > > Release |Scheduled Branch Cut|Scheduled Release Date > --------|--------------------|------------- > v1.17.0 |Nov 19, 2018 |Dec 4, 2018 > v1.18.0 |Jan 2, 2019 |Jan 15, 2019 > v1.19.0 |Feb 12, 2019 |Feb 26, 2019 > v1.20.0 |Mar 26, 2019 |Apr 9, 2019 > v1.21.0 |May 7, 2019 |May 21, 2019 > v1.22.0 |Jun 18, 2019 |Jul 2, 2019 > v1.23.0 |Jul 30, 2019 |Aug 13, 2019Commits
- [`fe494ff`](https://github.com/grpc/grpc/commit/fe494ff4104b6f6a78117ab2da71d29c93053267) Merge pull request [#20458](https://github-redirect.dependabot.com/grpc/grpc/issues/20458) from veblush/v1.24.1 - [`397cff4`](https://github.com/grpc/grpc/commit/397cff49acb4f56f59ebb1f5e7fb764389f7a414) Merge pull request [#20457](https://github-redirect.dependabot.com/grpc/grpc/issues/20457) from veblush/v1.24.x-py-fix - [`5cbf8ea`](https://github.com/grpc/grpc/commit/5cbf8ead38bcf3473bac62646e1d419ba95dff3c) Regenerate projects - [`577ecfd`](https://github.com/grpc/grpc/commit/577ecfd76f2fb82efeda4eea9fbe560e24769109) Bump version to 1.24.1 - [`adc9848`](https://github.com/grpc/grpc/commit/adc9848e4c8ee4aaf4be4001f8a74b5068d74f1a) Fix python windows link problem - See full diff in [compare view](https://github.com/grpc/grpc/compare/v1.24.0...v1.24.1)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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)