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.

Sign up for GitHub

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

Jump to bottom

Lock file maintenance Python dependencies #159

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Lock file maintenance Python dependencies #159

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 9, 2024 •
edited
Loading

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
lockFileMaintenance All locks refreshed
cosl charm-libs patch 0.0.12 -> 0.0.45 age adoption passing confidence
cryptography (changelog) charm-libs patch 43.0.1 -> 43.0.3 age adoption passing confidence
jsonschema (changelog) charm-libs minor 4.22.0 -> 4.23.0 age adoption passing confidence
ops-scenario unit minor ^6.0.3, <6.0.4 -> ^6.1.7, <6.1.8 age adoption passing confidence
poetry-core dependencies patch ^1.9.0 -> ^1.9.1 age adoption passing confidence
pydantic (changelog) charm-libs patch 1.10.17 -> 1.10.19 age adoption passing confidence
pytest (changelog) integration minor ^8.2.2 -> ^8.3.4 age adoption passing confidence
pytest (changelog) unit minor ^8.2.2 -> ^8.3.4 age adoption passing confidence
pytest-operator integration minor ^0.35.0 -> ^0.38.0 age adoption passing confidence
ruff (source, changelog) lint minor ^0.4.5 -> ^0.8.1 age adoption passing confidence
ruff (source, changelog) format minor ^0.4.5 -> ^0.8.1 age adoption passing confidence

🔧 This Pull Request updates lock files to use the latest dependency versions.

Release Notes

canonical/cos-lib (cosl)

v0.0.45

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.44...0.0.45

v0.0.43

Compare Source

What's Changed

New Contributors

Full Changelog: canonical/cos-lib@0.0.42...0.0.43

v0.0.42

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.41...0.0.42

v0.0.41

Compare Source

Add LogForwarder in coordinator

v0.0.40

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.39...0.0.40

v0.0.39: Push root ca cert to workload container

Compare Source

v0.0.38: bump release tag to match pyproject.toml

Compare Source

v0.0.37: s3 TLS support

Compare Source

added support for s3 TLS
minor touches to coordinator status

v0.0.36

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.34...0.0.36

v0.0.34: Fixed retry logic in worker object

Compare Source

v0.0.33: refactored worker status logic

Compare Source

refactored worker status logic

v0.0.32

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.31...0.0.32

v0.0.31

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.30...0.0.31

v0.0.30: holistic worker logic

Compare Source

refactored Worker logic to use a stateless reconciler function to avoid some pod-churn related race conditions

v0.0.29

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.28...0.0.29

v0.0.28

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.27...0.0.28

v0.0.27

Compare Source

unified config accessing logic so that it can be overridden by worker subclasses if a worker charm needs to preprocess its config on a per-unit basis

v0.0.26

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.25...0.0.26

v0.0.25

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.24...0.0.25

v0.0.24

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.23...0.0.24

v0.0.23: worker status checks TLS support

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.22...0.0.23

v0.0.22: Worker service status monitoring

Compare Source

The main feature is an update to the Coordinator-Worker classes, introducing a pebble-checks-based API to monitor the health of the worker service and set application status accordingly.
This takes care of some bugs we experienced in the past where the worker would not start and the admin had no way to notice it if not to manually GET a /ready endpoint on the application IP.

What's Changed

Full Changelog: canonical/cos-lib@0.0.21...0.0.22

v0.0.21

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.20...0.0.21

v0.0.20: Fix removeprefix for python3.8

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.19...0.0.20

v0.0.19

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.18...0.0.19

v0.0.18

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.17...0.0.18

v0.0.17

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.16...0.0.17

v0.0.16

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.14...0.0.16

v0.0.15

Compare Source

What's Changed

New Contributors

Full Changelog: canonical/cos-lib@0.0.13...0.0.15

v0.0.14

Compare Source

v0.0.13

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.12...0.0.13

pyca/cryptography (cryptography)

v43.0.3

Compare Source

python-jsonschema/jsonschema (jsonschema)

v4.23.0

Compare Source

=======

  • Do not reorder dictionaries (schemas, instances) that are printed as part of validation errors.
  • Declare support for Py3.13
canonical/ops-scenario (ops-scenario)

v6.1.7

Compare Source

v6.1.6

Compare Source

v6.1.5

Compare Source

v6.1.4

Compare Source

v6.1.3

Compare Source

v6.1.2

Compare Source

v6.1.1

Compare Source

v6.1.0

Compare Source

v6.0.5

Compare Source

v6.0.4

Compare Source

python-poetry/poetry-core (poetry-core)

v1.9.1

Compare Source

Added
  • Add 3.13 to the list of available Python versions (#​747).
pydantic/pydantic (pydantic)

v1.10.19

Compare Source

v1.10.18

Compare Source

pytest-dev/pytest (pytest)

v8.3.4

Compare Source

pytest 8.3.4 (2024-12-01)

Bug fixes

  • #​12592: Fixed KeyError{.interpreted-text role="class"} crash when using --import-mode=importlib in a directory layout where a directory contains a child directory with the same name.

  • #​12818: Assertion rewriting now preserves the source ranges of the original instructions, making it play well with tools that deal with the AST, like executing.

  • #​12849: ANSI escape codes for colored output now handled correctly in pytest.fail{.interpreted-text role="func"} with [pytrace=False]{.title-ref}.

  • #​9353: pytest.approx{.interpreted-text role="func"} now uses strict equality when given booleans.

Improved documentation

  • #​10558: Fix ambiguous docstring of pytest.Config.getoption{.interpreted-text role="func"}.

  • #​10829: Improve documentation on the current handling of the --basetemp option and its lack of retention functionality (temporary directory location and retention{.interpreted-text role="ref"}).

  • #​12866: Improved cross-references concerning the recwarn{.interpreted-text role="fixture"} fixture.

  • #​12966: Clarify filterwarnings{.interpreted-text role="ref"} docs on filter precedence/order when using multiple @pytest.mark.filterwarnings <pytest.mark.filterwarnings ref>{.interpreted-text role="ref"} marks.

Contributor-facing changes

  • #​12497: Fixed two failing pdb-related tests on Python 3.13.

v8.3.3

Compare Source

pytest 8.3.3 (2024-09-09)

Bug fixes

  • #​12446: Avoid calling @property (and other instance descriptors) during fixture discovery -- by asottile{.interpreted-text role="user"}

  • #​12659: Fixed the issue of not displaying assertion failure differences when using the parameter --import-mode=importlib in pytest>=8.1.

  • #​12667: Fixed a regression where type change in [ExceptionInfo.errisinstance]{.title-ref} caused [mypy]{.title-ref} to fail.

  • #​12744: Fixed typing compatibility with Python 3.9 or less -- replaced [typing.Self]{.title-ref} with [typing_extensions.Self]{.title-ref} -- by Avasam{.interpreted-text role="user"}

  • #​12745: Fixed an issue with backslashes being incorrectly converted in nodeid paths on Windows, ensuring consistent path handling across environments.

  • #​6682: Fixed bug where the verbosity levels where not being respected when printing the "msg" part of failed assertion (as in assert condition, msg).

  • #​9422: Fix bug where disabling the terminal plugin via -p no:terminal would cause crashes related to missing the verbose option.

    -- by GTowers1{.interpreted-text role="user"}

Improved documentation

  • #​12663: Clarify that the [pytest_deselected]{.title-ref} hook should be called from [pytest_collection_modifyitems]{.title-ref} hook implementations when items are deselected.
  • #​12678: Remove erroneous quotes from [tmp_path_retention_policy]{.title-ref} example in docs.

Miscellaneous internal changes

  • #​12769: Fix typos discovered by codespell and add codespell to pre-commit hooks.

v8.3.2

Compare Source

pytest 8.3.2 (2024-07-24)

Bug fixes

  • #​12652: Resolve regression [conda]{.title-ref} environments where no longer being automatically detected.

    -- by RonnyPfannschmidt{.interpreted-text role="user"}

v8.3.1

Compare Source

pytest 8.3.1 (2024-07-20)

The 8.3.0 release failed to include the change notes and docs for the release. This patch release remedies this. There are no other changes.

v8.3.0

Compare Source

pytest 8.3.0 (2024-07-20)

New features

  • #​12231: Added [--xfail-tb]{.title-ref} flag, which turns on traceback output for XFAIL results.

    • If the [--xfail-tb]{.title-ref} flag is not given, tracebacks for XFAIL results are NOT shown.
    • The style of traceback for XFAIL is set with [--tb]{.title-ref}, and can be [auto|long|short|line|native|no]{.title-ref}.
    • Note: Even if you have [--xfail-tb]{.title-ref} set, you won't see them if [--tb=no]{.title-ref}.

    Some history:

    With pytest 8.0, [-rx]{.title-ref} or [-ra]{.title-ref} would not only turn on summary reports for xfail, but also report the tracebacks for xfail results. This caused issues with some projects that utilize xfail, but don't want to see all of the xfail tracebacks.

    This change detaches xfail tracebacks from [-rx]{.title-ref}, and now we turn on xfail tracebacks with [--xfail-tb]{.title-ref}. With this, the default [-rx]{.title-ref}/ [-ra]{.title-ref} behavior is identical to pre-8.0 with respect to xfail tracebacks. While this is a behavior change, it brings default behavior back to pre-8.0.0 behavior, which ultimately was considered the better course of action.

  • #​12281: Added support for keyword matching in marker expressions.

    Now tests can be selected by marker keyword arguments.
    Supported values are int{.interpreted-text role="class"}, (unescaped) str{.interpreted-text role="class"}, bool{.interpreted-text role="class"} & None{.interpreted-text role="data"}.

    See marker examples <marker_keyword_expression_example>{.interpreted-text role="ref"} for more information.

    -- by lovetheguitar{.interpreted-text role="user"}

  • #​12567: Added --no-fold-skipped command line option.

    If this option is set, then skipped tests in short summary are no longer grouped
    by reason but all tests are printed individually with their nodeid in the same
    way as other statuses.

    -- by pbrezina{.interpreted-text role="user"}

Improvements in existing functionality

  • #​12469: The console output now uses the "third-party plugins" terminology,
    replacing the previously established but confusing and outdated
    reference to setuptools <setuptools:index>{.interpreted-text role="std:doc"}
    -- by webknjaz{.interpreted-text role="user"}.

  • #​12544, #​12545: Python virtual environment detection was improved by
    checking for a pyvenv.cfg{.interpreted-text role="file"} file, ensuring reliable detection on
    various platforms -- by zachsnickers{.interpreted-text role="user"}.

  • #​2871: Do not truncate arguments to functions in output when running with [-vvv]{.title-ref}.

  • #​389: The readability of assertion introspection of bound methods has been enhanced
    -- by farbodahm{.interpreted-text role="user"}, webknjaz{.interpreted-text role="user"}, obestwalter{.interpreted-text role="user"}, flub{.interpreted-text role="user"}
    and glyphack{.interpreted-text role="user"}.

    Earlier, it was like:

    =================================== FAILURES ===================================
_____________________________________ test _____________________________________

    def test():
>       assert Help().fun() == 2
E       assert 1 == 2
E        +  where 1 = <bound method Help.fun of <example.Help instance at 0x256a830>>()
E        +    where <bound method Help.fun of <example.Help instance at 0x256a830>> = <example.Help instance at 0x256a830>.fun
E        +      where <example.Help instance at 0x256a830> = Help()

example.py:7: AssertionError
=========================== 1 failed in 0.03 seconds ===========================

    And now it's like:

    =================================== FAILURES ===================================
_____________________________________ test _____________________________________

    def test():
>       assert Help().fun() == 2
E       assert 1 == 2
E        +  where 1 = fun()
E        +    where fun = <test_local.Help object at 0x1074be230>.fun
E        +      where <test_local.Help object at 0x1074be230> = Help()

test_local.py:13: AssertionError
=========================== 1 failed in 0.03 seconds ===========================

  • #​7662: Added timezone information to the testsuite timestamp in the JUnit XML report.

Bug fixes

  • #​11706: Fixed reporting of teardown errors in higher-scoped fixtures when using [--maxfail]{.title-ref} or [--stepwise]{.title-ref}.

    Originally added in pytest 8.0.0, but reverted in 8.0.2 due to a regression in pytest-xdist.
    This regression was fixed in pytest-xdist 3.6.1.

  • #​11797: pytest.approx{.interpreted-text role="func"} now correctly handles Sequence <collections.abc.Sequence>{.interpreted-text role="class"}-like objects.

  • #​12204, #​12264: Fixed a regression in pytest 8.0 where tracebacks get longer and longer when multiple
    tests fail due to a shared higher-scope fixture which raised -- by bluetech{.interpreted-text role="user"}.

    Also fixed a similar regression in pytest 5.4 for collectors which raise during setup.

    The fix necessitated internal changes which may affect some plugins:

    • FixtureDef.cached_result[2] is now a tuple (exc, tb)
      instead of exc.
    • SetupState.stack failures are now a tuple (exc, tb)
      instead of exc.

  • #​12275: Fixed collection error upon encountering an abstract <abc>{.interpreted-text role="mod"} class, including abstract [unittest.TestCase]{.title-ref} subclasses.

  • #​12328: Fixed a regression in pytest 8.0.0 where package-scoped parameterized items were not correctly reordered to minimize setups/teardowns in some cases.

  • #​12424: Fixed crash with [assert testcase is not None]{.title-ref} assertion failure when re-running unittest tests using plugins like pytest-rerunfailures. Regressed in 8.2.2.

  • #​12472: Fixed a crash when returning category "error" or "failed" with a custom test status from pytest_report_teststatus{.interpreted-text role="hook"} hook -- pbrezina{.interpreted-text role="user"}.

  • #​12505: Improved handling of invalid regex patterns in pytest.raises(match=r'...') <pytest.raises>{.interpreted-text role="func"} by providing a clear error message.

  • #​12580: Fixed a crash when using the cache class on Windows and the cache directory was created concurrently.

  • #​6962: Parametrization parameters are now compared using [==]{.title-ref} instead of [is]{.title-ref} ([is]{.title-ref} is still used as a fallback if the parameter does not support [==]{.title-ref}).
    This fixes use of parameters such as lists, which have a different [id]{.title-ref} but compare equal, causing fixtures to be re-computed instead of being cached.

  • #​7166: Fixed progress percentages (the [ 87%] at the edge of the screen) sometimes not aligning correctly when running with pytest-xdist -n.

Improved documentation

  • #​12153: Documented using PYTEST_VERSION{.interpreted-text role="envvar"} to detect if code is running from within a pytest run.

  • #​12469: The external plugin mentions in the documentation now avoid mentioning
    setuptools entry-points <setuptools:index>{.interpreted-text role="std:doc"} as the concept is
    much more generic nowadays. Instead, the terminology of "external",
    "installed", or "third-party" plugins (or packages) replaces that.

    -- by webknjaz{.interpreted-text role="user"}

  • #​12577: [CI]{.title-ref} and [BUILD_NUMBER]{.title-ref} environment variables role is discribed in
    the reference doc. They now also appear when doing [pytest -h]{.title-ref}
    -- by MarcBresson{.interpreted-text role="user"}.

Contributor-facing changes

  • #​12467: Migrated all internal type-annotations to the python3.10+ style by using the [annotations]{.title-ref} future import.

    -- by RonnyPfannschmidt{.interpreted-text role="user"}

  • #​11771, #​12557: The PyPy runtime version has been updated to 3.9 from 3.8 that introduced
    a flaky bug at the garbage collector which was not expected to fix there
    as the 3.8 is EoL.

    -- by x612skm{.interpreted-text role="user"}

  • #​12493: The change log draft preview integration has been refactored to use a
    third party extension sphinxcontib-towncrier. The previous in-repo
    script was putting the change log preview file at
    doc/en/_changelog_towncrier_draft.rst{.interpreted-text role="file"}. Said file is no longer
    ignored in Git and might show up among untracked files in the
    development environments of the contributors. To address that, the
    contributors can run the following command that will clean it up:

    $ git clean -x -i -- doc/en/_changelog_towncrier_draft.rst

    -- by webknjaz{.interpreted-text role="user"}

  • #​12498: All the undocumented tox environments now have descriptions.
    They can be listed in one's development environment by invoking
    tox -av in a terminal.

    -- by webknjaz{.interpreted-text role="user"}

  • #​12501: The changelog configuration has been updated to introduce more accurate
    audience-tailored categories. Previously, there was a trivial
    change log fragment type with an unclear and broad meaning. It was
    removed and we now have contrib, misc and packaging in
    place of it.

    The new change note types target the readers who are downstream
    packagers and project contributors. Additionally, the miscellaneous
    section is kept for unspecified updates that do not fit anywhere else.

    -- by webknjaz{.interpreted-text role="user"}

  • #​12502: The UX of the GitHub automation making pull requests to update the
    plugin list has been updated. Previously, the maintainers had to close
    the automatically created pull requests and re-open them to trigger the
    CI runs. From now on, they only need to click the [Ready for review]{.title-ref}
    button instead.

    -- by webknjaz{.interpreted-text role="user"}

  • #​12522: The :pull: RST role has been replaced with a shorter
    :pr: due to starting to use the implementation from
    the third-party sphinx-issues{.interpreted-text role="pypi"} Sphinx extension
    -- by webknjaz{.interpreted-text role="user"}.

  • #​12531: The coverage reporting configuration has been updated to exclude
    pytest's own tests marked as expected to fail from the coverage
    report. This has an effect of reducing the influence of flaky
    tests on the resulting number.

    -- by webknjaz{.interpreted-text role="user"}

  • #​12533: The extlinks Sphinx extension is no longer enabled. The :bpo:
    role it used to declare has been removed with that. BPO itself has
    migrated to GitHub some years ago and it is possible to link the
    respective issues by using their GitHub issue numbers and the
    :issue: role that the sphinx-issues extension implements.

    -- by webknjaz{.interpreted-text role="user"}

  • #​12562: Possible typos in using the :user: RST role is now being linted
    through the pre-commit tool integration -- by webknjaz{.interpreted-text role="user"}.

charmed-kubernetes/pytest-operator (pytest-operator)

v0.37.0: 0.37.0

Compare Source

astral-sh/ruff (ruff)

v0.8.1

Compare Source

Preview features
  • Formatter: Avoid invalid syntax for format-spec with quotes for all Python versions (#​14625)
  • Formatter: Consider quotes inside format-specs when choosing the quotes for an f-string (#​14493)
  • Formatter: Do not consider f-strings with escaped newlines as multiline (#​14624)
  • Formatter: Fix f-string formatting in assignment statement (#​14454)
  • Formatter: Fix unnecessary space around power operator (**) in overlong f-string expressions (#​14489)
  • [airflow] Avoid implicit schedule argument to DAG and @dag (AIR301) (#​14581)
  • [flake8-builtins] Exempt private built-in modules (A005) (#​14505)
  • [flake8-pytest-style] Fix pytest.mark.parametrize rules to check calls instead of decorators (#​14515)
  • [flake8-type-checking] Implement runtime-cast-value (TC006) (#​14511)
  • [flake8-type-checking] Implement unquoted-type-alias (TC007) and quoted-type-alias (TC008) (#​12927)
  • [flake8-use-pathlib] Recommend Path.iterdir() over os.listdir() (PTH208) (#​14509)
  • [pylint] Extend invalid-envvar-default to detect os.environ.get (PLW1508) (#​14512)
  • [pylint] Implement len-test (PLC1802) (#​14309)
  • [refurb] Fix bug where methods defined using lambdas were flagged by FURB118 (#​14639)
  • [ruff] Auto-add r prefix when string has no backslashes for unraw-re-pattern (RUF039) (#​14536)
  • [ruff] Implement invalid-assert-message-literal-argument (RUF040) (#​14488)
  • [ruff] Implement unnecessary-nested-literal (RUF041) (#​14323)
  • [ruff] Implement unnecessary-regular-expression (RUF055) (#​14659)
Rule changes
  • Ignore more rules for stub files (#​14541)
  • [pep8-naming] Eliminate false positives for single-letter names (N811, N814) (#​14584)
  • [pyflakes] Avoid false positives in @no_type_check contexts (F821, F722) (#​14615)
  • [ruff] Detect redirected-noqa in file-level comments (RUF101) (#​14635)
  • [ruff] Mark fixes for unsorted-dunder-all and unsorted-dunder-slots as unsafe when there are complex comments in the sequence (RUF022, RUF023) (#​14560)
Bug fixes
  • Avoid fixing code to None | None for redundant-none-literal (PYI061) and never-union (RUF020) (#​14583, #​14589)
  • [flake8-bugbear] Fix mutable-contextvar-default to resolve annotated function calls properly (B039) (#​14532)
  • [flake8-pyi, ruff] Fix traversal of nested literals and unions (PYI016, PYI051, PYI055, PYI062, RUF041) (#​14641)
  • [flake8-pyi] Avoid rewriting invalid type expressions in unnecessary-type-union (PYI055) (#​14660)
  • [flake8-type-checking] Avoid syntax errors and type checking problem for quoted annotations autofix (TC003, TC006) (#​14634)
  • [pylint] Do not wrap function calls in parentheses in the fix for unnecessary-dunder-call (PLC2801) (#​14601)
  • [ruff] Handle attrs's auto_attribs correctly (RUF009) (#​14520)

v0.8.0

Compare Source

Check out the blog post for a migration guide and overview of the changes!

Breaking changes

See also, the "Remapped rules" section which may result in disabled rules.

  • Default to Python 3.9

    Ruff now defaults to Python 3.9 instead of 3.8 if no explicit Python version is configured using ruff.target-version or project.requires-python (#​13896)

  • Changed location of pydoclint diagnostics

    pydoclint diagnostics now point to the first-line of the problematic docstring. Previously, this was not the case.

    If you've opted into these preview rules but have them suppressed using
    noqa comments in
    some places, this change may mean that you need to move the noqa suppression
    comments. Most users should be unaffected by this change.

  • Use XDG (i.e. ~/.local/bin) instead of the Cargo home directory in the standalone installer

    Previously, Ruff's installer used $CARGO_HOME or ~/.cargo/bin for its target install directory. Now, Ruff will be installed into $XDG_BIN_HOME, $XDG_DATA_HOME/../bin, or ~/.local/bin (in that order).

    This change is only relevant to users of the standalone Ruff installer (using the shell or PowerShell script). If you installed Ruff using uv or pip, you should be unaffected.

  • Changes to the line width calculation

    Ruff now uses a new version of the unicode-width Rust crate to calculate the line width. In very rare cases, this may lead to lines containing Unicode characters being reformatted, or being considered too long when they were not before (E501).

Removed Rules

The following deprecated rules have been removed:

Remapped rules

The following rules have been remapped to new rule codes:

Stabilization

The following rules have been stabilized and are no longer in preview:

Configuration

📅 Schedule: Branch creation - "after 1am and before 3am every weekday" in timezone Etc/UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

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

@renovate renovate bot requested review from a team, paulomach, taurus-forever, shayancanonical and carlcsaposs-canonical and removed request for a team July 9, 2024 01:09
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Jul 9, 2024 •
edited
Loading

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

Creating virtualenv charm-88ziTglk-py3.13 in /home/ubuntu/.cache/pypoetry/virtualenvs

Because ops-scenario (6.1.7) depends on ops (>=2.12,<=2.16)
 and no versions of ops-scenario match >6.1.7,<6.1.8, ops-scenario (>=6.1.7,<6.1.8) requires ops (>=2.12,<=2.16).
So, because charm depends on both ops (>=2.9.0,<2.10) and ops-scenario (^6.1.7, <6.1.8), version solving failed.

@renovate renovate bot force-pushed the renovate/python-dependencies branch from 83f9b4b to 925f685 Compare July 10, 2024 01:44
taurus-forever
taurus-forever reviewed Jul 15, 2024
View reviewed changes
Copy link
Contributor

@taurus-forever taurus-forever left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@carlcsaposs-canonical any ideas why lint is not happy here?

@renovate renovate bot force-pushed the renovate/python-dependencies branch 2 times, most recently from 01e1a9e to 1d3b59b Compare July 25, 2024 01:30
@carlcsaposs-canonical
Copy link
Contributor

@carlcsaposs-canonical any ideas why lint is not happy here?

#159 (comment)

@renovate renovate bot force-pushed the renovate/python-dependencies branch from 1d3b59b to 20dd0f9 Compare July 26, 2024 01:26
@renovate renovate bot force-pushed the renovate/python-dependencies branch from 20dd0f9 to 33c0c94 Compare August 8, 2024 01:18
@renovate renovate bot force-pushed the renovate/python-dependencies branch from 33c0c94 to 1a09e29 Compare August 20, 2024 01:17
@renovate renovate bot force-pushed the renovate/python-dependencies branch from 1a09e29 to cacf9b8 Compare August 29, 2024 02:24
@renovate renovate bot force-pushed the renovate/python-dependencies branch 2 times, most recently from 66a39db to f27b39d Compare September 11, 2024 01:18
@renovate renovate bot force-pushed the renovate/python-dependencies branch 2 times, most recently from 473af02 to 76b8f8a Compare October 2, 2024 01:36
@renovate renovate bot force-pushed the renovate/python-dependencies branch 3 times, most recently from 1c2e990 to 7f5bf70 Compare October 15, 2024 20:50
@renovate renovate bot force-pushed the renovate/python-dependencies branch 2 times, most recently from 814b971 to e026879 Compare October 25, 2024 01:12
@renovate renovate bot force-pushed the renovate/python-dependencies branch 2 times, most recently from e9a2f6c to b513b82 Compare November 18, 2024 01:10
@renovate renovate bot force-pushed the renovate/python-dependencies branch 2 times, most recently from 9934558 to af2af3c Compare November 28, 2024 01:44
@renovate renovate bot force-pushed the renovate/python-dependencies branch from af2af3c to 7ff6a62 Compare December 4, 2024 02:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@taurus-forever taurus-forever taurus-forever left review comments

@paulomach paulomach Awaiting requested review from paulomach paulomach was automatically assigned from canonical/data-platform-mysql

@shayancanonical shayancanonical Awaiting requested review from shayancanonical shayancanonical was automatically assigned from canonical/data-platform-mysql

@carlcsaposs-canonical carlcsaposs-canonical Awaiting requested review from carlcsaposs-canonical carlcsaposs-canonical was automatically assigned from canonical/data-platform-mysql

At least 2 approving reviews are required to merge this pull request.

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@carlcsaposs-canonical @taurus-forever