Feature build update - Githubissues

Proposed changes

Upstream pipenv package or dependency had change in how package versions are specified. Modified files to match.

Types of changes

What types of changes does your code introduce to dbldatagen? Put an x in the boxes that apply

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Change to tutorials, tests or examples
[x] Non code change (readme, images or other non-code assets)
[ ] Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules
[x] Submission does not reduce code coverage numbers
[x] Submission does not increase alerts or messages from prospector / lint

Further comments

Non code change - needed due to upstream change in building mechanism. Increased build version in prep for next release also

databrickslabs / dbldatagen

Feature build update #220

Proposed changes

Types of changes

Checklist

Further comments

Codecov Report