Add explicit GHSA for vuln disclosure #903
Merged
Conversation
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
Replaced deprecated ruff config
Removing date from copyrights to ease maintenance is the practice nowadays, see https://aboutcode.org/2023/update-copyright-each-new-year/
Based on latest https://opensource.org/license/BSD-3-Clause, suggested removal of ambiguity from https://peps.python.org/pep-0639/appendix-mapping-classifiers/ and https://peps.python.org/pep-0639/#deprecate-license-classifiers Fixed #896
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Added similar behaviors to all interfaces where expires_at is parsed, this will facilitate the implementations. Note this is breaking change for those which are expecting the "default" `expires_at` (as in, not provided) to be a float. This will now default to a int.
auvipy
approved these changes
Jun 18, 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.
During the last CVE disclosure, it was not obvious which tools shall we use to discuss about the vulnerability.
Replacing email with GitHub private channel with oauthlib administrators has been found very convenient and should be listed explicitly when raising issues.