Repository navigation
Conversation
10 of 16 tasks
Preserve the two cleanup commits from eigenmannmartin#180 alongside the publishing workflow. Keep the resolved urllib3 lock and check calendar property content across icalendar versions.
jezdez
changed the title
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.
Integrate Martin's cleanup from #180 with destination publishing. Keep Python 3.10 as the minimum, Poetry 2.1.2 and master's urllib3 update. Check the preserved calendar field value without relying on icalendar's property class hierarchy.
Release tags build distributions and publish through the pypi environment using Trusted Publishing. Configure the protected GitHub environment and matching PyPI publisher before the next planned release.