-
Notifications
You must be signed in to change notification settings - Fork 9
chore(deps): update dependency pep8-naming to v0.15.1 #574
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 and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
+1
−1
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
Contributor
Author
⚠️ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you click the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: poetry.lock
Updating dependencies
Resolving dependencies...
The current project's supported Python range (>=3.8.1,<4.0) is not compatible with some of the required packages Python requirement:
- pep8-naming requires Python >=3.9, so it will not be satisfied for Python >=3.8.1,<3.9
Because descope depends on pep8-naming (0.15.1) which requires Python >=3.9, version solving failed.
• Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties
For pep8-naming, a possible solution would be to set the `python` property to ">=3.9,<4.0"
https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
https://python-poetry.org/docs/dependency-specification/#using-environment-markers
@descope
descope
bot
force-pushed
the
renovate/pep8-naming-0.x
branch
from
May 20, 2025 17:11
6f99e4e to
516a1d6
Compare
@descope
descope
bot
force-pushed
the
renovate/pep8-naming-0.x
branch
from
May 21, 2025 14:42
516a1d6 to
2056e7c
Compare
@descope
descope
bot
force-pushed
the
renovate/pep8-naming-0.x
branch
from
May 23, 2025 10:38
2056e7c to
9c234f7
Compare
@descope
descope
bot
force-pushed
the
renovate/pep8-naming-0.x
branch
from
May 23, 2025 19:41
9c234f7 to
083162f
Compare
@descope
descope
bot
force-pushed
the
renovate/pep8-naming-0.x
branch
from
May 25, 2025 15:50
083162f to
0b5fa75
Compare
@descope
descope
bot
force-pushed
the
renovate/pep8-naming-0.x
branch
from
May 25, 2025 21:22
0b5fa75 to
52e8d01
Compare
@descope
descope
bot
force-pushed
the
renovate/pep8-naming-0.x
branch
from
May 26, 2025 21:21
52e8d01 to
5f44baa
Compare
@descope
descope
bot
changed the title
(削除) chore(deps): update dependency pep8-naming to v0.15.0 (削除ここまで)
(追記) chore(deps): update dependency pep8-naming to v0.15.1 (追記ここまで)
May 26, 2025
@descope
descope
bot
force-pushed
the
renovate/pep8-naming-0.x
branch
from
May 28, 2025 07:22
5f44baa to
1512808
Compare
@descope
descope
bot
force-pushed
the
renovate/pep8-naming-0.x
branch
from
June 1, 2025 01:03
1512808 to
a0af9be
Compare
@descope
descope
bot
force-pushed
the
renovate/pep8-naming-0.x
branch
from
June 2, 2025 23:39
a0af9be to
3c5b25f
Compare
@descope
descope
bot
force-pushed
the
renovate/pep8-naming-0.x
branch
from
June 3, 2025 20:33
3c5b25f to
a021892
Compare
@descope
descope
bot
force-pushed
the
renovate/pep8-naming-0.x
branch
from
June 7, 2025 19:34
a021892 to
86e5dce
Compare
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.
Uh oh!
There was an error while loading. Please reload this page.
This PR contains the following updates:
0.14.1→0.15.1Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
PyCQA/pep8-naming (pep8-naming)
v0.15.1Compare Source
v0.15.0Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.