Update Releases Batched for Next (next) #2170
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
⚠ Artifact update problemRenovate failed to update artifacts 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:
The artifact failure details are included below: File name: poetry.lockFile name: poetry.lock |
renovate
bot
force-pushed
the
renovate/next-releases-batched-for-next
branch
3 times, most recently
from
eaa4c2a
to
e927999
Compare
renovate
bot
force-pushed
the
renovate/next-releases-batched-for-next
branch
3 times, most recently
from
2f2abae
to
d0231f2
Compare
renovate
bot
force-pushed
the
renovate/next-releases-batched-for-next
branch
2 times, most recently
from
62edb25
to
16fc35e
Compare
renovate
bot
force-pushed
the
renovate/next-releases-batched-for-next
branch
from
16fc35e
to
5002f68
Compare
pyproject.toml
Outdated
| @@ -43,9 +43,9 @@ django-auth-ldap = {version = "~4.1.0", optional = true} | |||
| # Caching with Redis | |||
| django-cacheops = "~6.0" | |||
| # Base functionality for task scheduling with Celery | |||
| django-celery-beat = "~2.2.1" | |||
| django-celery-beat = "~2.3.0" | |||
There was a problem hiding this comment.
Change/potential breakage: celery/django-celery-beat#525
There was a problem hiding this comment.
Also celery/django-celery-beat#528 - now requires upgrading to django-timezone-field >= 5.0. Will investigate if this is feasible.
There was a problem hiding this comment.
Spent far too much time digging into a migration error resulting from this update, but finally opened mfogel/django-timezone-field#96
pyproject.toml
Outdated
| # Optional data validation of config contexts | ||
| jsonschema = "~4.7.0" | ||
| # Rendering of markdown files to HTML | ||
| Markdown = "~3.3.7" | ||
| Markdown = "~3.4.0" |
There was a problem hiding this comment.
Similarly, removes deprecated code (https://github.com/Python-Markdown/markdown/blob/master/docs/change_log/release-3.4.md#previously-deprecated-objects-have-been-removed) but doesn't look like any of those changes should impact Nautobot core.
There was a problem hiding this comment.
Actually, there are apparently a number of extensions that haven't been updated and still depend on these deprecated features, which caused mkdocs to pin to Markdown < 3.4 at present. So upgrading Markdown to 3.4 actually forces mkdocs to downgrade from 1.3.1 (which has the pin) to 1.3.0 (which does not).
In short: do we want to prioritize latest Markdown or latest mkdocs, because we can't have both at this time.
There was a problem hiding this comment.
This PR contains the following updates:
~3.0.3->~3.1.0==3.0.3->==3.1.2~3.3.7->~3.4.0~22.6.0->~22.8.06.0->6.1~2.2.1->~2.3.0~2.8.0->~2.9.01.0->1.1~3.5.0->~3.6.03.2.0->3.2.1~1.12.3->~1.13.0~0.22.1->~0.23.0~4.7.0->~4.16.0~3.6.0->~3.7.0==3.6.1->==3.7.18.4.2->8.4.3==8.4.2->==8.4.3~2.27.1->~2.28.0~4.3.0->~4.4.0Configuration
📅 Schedule: Branch creation - "before 2am" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.