Skip to content
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

fix(deps): update dependency flask-caching to ^2.3.0 - autoclosed #3793

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Oct 8, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
Flask-Caching (changelog) ^2.0.1 -> ^2.3.0 age adoption passing confidence
flask-caching (changelog) ==2.0.1 -> ==2.3.0 age adoption passing confidence

Release Notes

pallets-eco/flask-caching (Flask-Caching)

v2.3.0

Released 2024-05-04

  • Added response_hit_indication flag to Cache.cached decorator for appending 'hit_cache' headers to responses, indicating cache hits.

v2.2.0

Compare Source

  • Drop python 3.7 support
  • python 3.11 officially supported
  • Fix issue causing args_to_ignore to not work with flask_caching.Cache.memoize decorator when keyword arguments were used in the decorated function call

v2.1.0

Compare Source

Released 2024-10-08

  • fix type signature in flask_caching.utils.make_template_fragment_key. :pr:430
  • Added docs and example for make_cache_key
  • support Flask 3

v2.0.2

Compare Source

Released 2023-01-12

  • fix issue with boto3 dependencie due to latest cachelib released
  • migrate flask_caching.backends.RedisCluster dependency from redis-py-cluster to redis-py
  • bug fix: make the make_cache_key attributed of decorated view functions writeable. :pr:431, :issue:97

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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 these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link
Author

renovate bot commented Oct 8, 2024

⚠️ 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...


Because flask-caching (2.3.0) depends on cachelib (>=0.9.0,<0.10.0)
 and no versions of flask-caching match >2.3.0,<3.0.0, Flask-Caching (>=2.3.0,<3.0.0) requires cachelib (>=0.9.0,<0.10.0).
So, because clashleaders depends on both Flask-Caching (^2.3.0) and cachelib (^0.10.2), version solving failed.

@renovate renovate bot force-pushed the renovate/flask-caching-2.x branch 8 times, most recently from 33eaf53 to 2a717b5 Compare October 10, 2024 15:59
@renovate renovate bot force-pushed the renovate/flask-caching-2.x branch 3 times, most recently from 7d6fc42 to b0338b2 Compare October 25, 2024 17:46
@renovate renovate bot force-pushed the renovate/flask-caching-2.x branch from b0338b2 to 60785e4 Compare October 25, 2024 19:53
@renovate renovate bot changed the title fix(deps): update dependency flask-caching to ^2.3.0 fix(deps): update dependency flask-caching to ^2.3.0 - autoclosed Oct 25, 2024
@renovate renovate bot closed this Oct 25, 2024
@renovate renovate bot deleted the renovate/flask-caching-2.x branch October 25, 2024 19:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants