Repository navigation
Bump the version to 5.7.0 and write the release section of the changelog - #15
Merged
Merged
Conversation
…ng a 100 ms timer, which failed twice on slow Windows runners
…orker's tearDown cannot clear another worker's keys
….7.0 changelog section
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The version bump for the first release under the
diskcache-communityname.diskcache/__init__.py:__version__5.7.0,__build__0x050700.pyproject.tomlanddocs/conf.pyread the version from there.CHANGELOG.md:Unreleasedbecomes5.7.0 (unreleased)with an introduction (what the release is, what stays compatible) and entries for PRs 12, 13 and 14; the release workflow publishes this section as the GitHub release notes.README.rst: the fork notice says 5.7.0 is the first release instead of "no release has been published yet".SECURITY.md: the CVE section describes 5.7.0 (defaultDiskunchanged, opt-inSafeDisk,0700directories) instead of the state ofmaster, and the supported-versions text drops the pre-release sentence.Do not merge until the
pypiandtestpypienvironments exist with their required reviewer, the pending trusted publishers are registered on PyPI and TestPyPI, the publish action is on the Actions allow-list, and the TestPyPI dry run has passed. Right before merging, the heading gets its date. Thev5.7.0tag on the merge commit then triggers the release workflow.Verified locally:
python -m buildproducesdiskcache_community-5.7.0sdist and wheel,twine check --strictpasses, rstcheck, doc8 and the Sphinx build pass, 357 tests pass, andimport diskcachereports 5.7.0.