-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Bump coverage from 7.2.5 to 7.2.6 #342
Conversation
Bumps [coverage](https://github.com/nedbat/coveragepy) from 7.2.5 to 7.2.7. - [Release notes](https://github.com/nedbat/coveragepy/releases) - [Changelog](https://github.com/nedbat/coveragepy/blob/master/CHANGES.rst) - [Commits](nedbat/coveragepy@7.2.5...7.2.7) --- updated-dependencies: - dependency-name: coverage dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Because coverage.py's wheel is built for the beta and ABI-incompatible.
I've pushed to this branch with a potential fix for testing 3.12. We're stuck pinning to 3.12a4 due to #331, and coverage.py has now released wheels for 3.12. However, they're built against 3.12 beta which is ABI-incompatible with the pinned alpha: https://github.com/nedbat/coveragepy/releases/tag/7.2.7 Here's one suggestion, only build from source for 3.12. It makes it much slower (4m6s vs. 6s) because we're now building the other dependencies from source. They'll be cached, but caches are cleared if not used for a week and this repo isn't very busy. By the same token, maybe the slower build is fine? Or is there a better way? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm okay with this, but it does complicate the workflow file a little bit.
Is it essential that we use the latest version of coverage right now? Or could we just keep the ==7.2.5
pin for now (or just bump it to ==7.2.6
?), until we're able to test with Python >=3.12b1 in CI?
Good point, we don't actually need to update coverage at all right now. Let's do 7.2.6 and keep things simpler until we can use a beta. I'll update this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Bumps coverage from 7.2.5 to 7.2.7.
Changelog
Sourced from coverage's changelog.
Commits
27cabc2
docs: sample HTML for 7.2.751b3e82
docs: prep for 7.2.76df9ee5
fix: revert "Map also empty dictionaries to file" (#1629)586b1ee
chore: make upgrade86722e1
chore: make workflows44fd6f8
build: include 3.12 when building wheelsc6c88f2
style: fix the spacing of the changes entries5281c6c
build: don't search in cache directoriesb62fc41
docs: one new-in mention, and tweak the release how-to3741d0e
build: bump versionDependabot 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)