Repository navigation
fix: require icalendar 7.1.3 or newer - #340
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 🚀 New features to boost your workflow:
|
This branch was successfully deployed
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.
Our minimum of
icalendar>=7.0.2still allowed 7.1.0 to 7.1.2, which have a security issue (GHSA-cv84-9p8j-fj68). Most people would already get a newer version on a fresh install, but this makes sure nobody ends up on one of those. It also rules out 7.0.x, which isn't affected, but that's only a small upgrade.I ran the tests locally on 3.10 and 3.14 with both 7.1.3 and the locked 7.3.0 and they all pass.
Merging this releases 0.6.1, along with the 3.14 classifier from #338.