Skip to content
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

build: Restrict TensorFlow to v2.2.X and TensorFlow Probability to v0.10.X #999

Merged
merged 2 commits into from
Jul 27, 2020

Conversation

matthewfeickert
Copy link
Member

@matthewfeickert matthewfeickert commented Jul 27, 2020

Description

Resolves #998

As Issue #997 makes it clear that minor releases might as well be major releases for TensorFlow, then it is probably worth keeping tighter version constraints on TensorFlow and TensorFlow Probability release ranges and just watching the releases of both libraries TensorFlow and TensorFlow Probability to see when we can relax these.

Note that Issue #997 won't be resolved until TensorFlow Probability v0.11.0 can be released, and as a result of this the current release workflows will also be broken until v0.11.0 is released. This is a good illustration of the point that with TensorFlow we need to be more restirctive.

Checklist Before Requesting Reviewer

  • Tests are passing
  • "WIP" removed from the title of the pull request
  • Selected an Assignee for the PR to be responsible for the log summary

Before Merging

For the PR Assignees:

  • Summarize commit messages into a comprehensive review of the PR
* Restrict the release ranges of TensorFlow to v2.2.X and TensorFlow Probability to v0.10.X
   - Minor releases of TensorFlow can have conflicts with TensorFlow Probability that are volatile enough to act as major releases

@matthewfeickert matthewfeickert added the build Changes that affect the build system or external dependencies label Jul 27, 2020
@matthewfeickert matthewfeickert self-assigned this Jul 27, 2020
@matthewfeickert matthewfeickert added the fix A bug fix label Jul 27, 2020
@codecov
Copy link

codecov bot commented Jul 27, 2020

Codecov Report

Merging #999 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #999   +/-   ##
=======================================
  Coverage   96.65%   96.65%           
=======================================
  Files          59       59           
  Lines        3284     3284           
  Branches      455      455           
=======================================
  Hits         3174     3174           
  Misses         69       69           
  Partials       41       41           
Flag Coverage Δ
#unittests 96.65% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


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 60488cd...be11220. Read the comment docs.

@matthewfeickert matthewfeickert merged commit 85f130c into master Jul 27, 2020
@matthewfeickert matthewfeickert deleted the build/restrict-TF-and-TFP-versions branch July 27, 2020 23:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Changes that affect the build system or external dependencies fix A bug fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Keep tighter version constraints on TensorFlow releases
3 participants