Add range validation for toml files by dmitry-shibanov · Pull Request #726 · actions/setup-python (original) (raw)
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Conversation1 Commits2 Checks0 Files changed
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
[ Show hidden characters]({{ revealButtonHref }})
Description:
In scope of this pull request we add minor change to validate == for toml files.
Related issue:
#711
Check list:
- Mark if documentation changes are required.
- Mark if tests were added or updated to cover the changes.
To help us decide whether to implement a workaround, do you have a sense of whether it will be days, weeks, or months before this fix is released? Python 3.12.0 is scheduled to be released on October 2nd, and I imagine the GitHub-hosted runners will start upgrading to it roughly the week after.
renovate bot referenced this pull request in rpdelaney/downforeveryone
szinn referenced this pull request in szinn/k8s-homelab
tetele added a commit to tetele/hvac_group that referenced this pull request
petretiandrea referenced this pull request in petretiandrea/home-assistant-tapo-p100
Harmon758 added a commit to Harmon758/Harmonbot that referenced this pull request
welpaolo referenced this pull request in canonical/spark-k8s-toolkit-py
rpdelaney referenced this pull request in rpdelaney/uncolor
