Release prep: 8.0.2 #2654
Merged
Release prep: 8.0.2 #2654
Conversation
This file contains 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
build: pin urllib3<2.3 to accommodate our old fork of vcrpy Also includes slight `typing.cast()` changes to accommodate new version of flake8-type-checking.
privileges, url: fix privilege check in `.urlban` command family
safety: fix safeify_url() exception on python 3.11
bot: round rate limit `time_left` value up, eliminate microseconds
Well it's supposed to do that. I will attempt to tweak this config and make the branch name sopel/.github/workflows/ci.yml Lines 10 to 13 in 44bc866 |
|
OK, the CI configuration is now working as expected for |
Exirel
approved these changes
Feb 3, 2025
SnoopJ
approved these changes
Feb 4, 2025
|
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.
Trying out a new workflow: I've merged the changelog and backport branches for 8.0.2 into this PR, which will both run CI on the final result and allow other maintainers to give the overall patch a once-over before it gets merged for final release.
If we like doing things this way, we can use it for 8.1.0—and create (an) appropriate label(s) in the tracker for this type of PR.