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

chore(deps): update dependency mkdocstrings to ^0.19.0 #9

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 20, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
mkdocstrings (changelog) ^0.15.0 -> ^0.19.0 age adoption passing confidence

Release Notes

mkdocstrings/mkdocstrings

v0.19.0

Compare Source

Compare with 0.18.1

Highlights

We decided to deprecate a few things to pave the way towards a more
stable code base, bringing us closer to a v1.

  • Selection and rendering options are now combined into a single
    options key. Using the old keys will emit a deprecation warning.
  • The BaseCollector and BaseRenderer classes are deprecated in favor
    of BaseHandler, which merges their functionality. Using the old
    classes will emit a deprecation warning.

New versions of the Python handler and the legacy Python handler
were also released in coordination with mkdocstrings 0.19.
See their respective changelogs:
python,
python-legacy.
Most notably, the Python handler gained the members and filters options
that prevented many users to switch to it.

mkdocstrings stopped depending directly on the legacy Python handler.
It means you now have to explicitely depend on it, directly or through
the extra provided by mkdocstrings, if you want to continue using it.

Packaging / Dependencies
  • Stop depending directly on mkdocstrings-python-legacy (9055d58 by Timothée Mazzucotelli). Issue #​376
Features
Code Refactoring
  • Support options / deprecated options mix-up (7c71f26 by Timothée Mazzucotelli).
  • Deprecate watch feature in favor of MkDocs' built-in one (c20022e by Timothée Mazzucotelli).
  • Log relative template paths if possible, instead of absolute (91f5f83 by Timothée Mazzucotelli).
  • Deprecate selection and rendering YAML keys (3335310 by Timothée Mazzucotelli). PR #​420
  • Deprecate BaseCollector and BaseRenderer (eb822cb by Timothée Mazzucotelli). PR #​413

v0.18.1

Compare Source

Compare with 0.18.0

Bug Fixes
  • Don't preemptively register identifiers as anchors (c7ac043 by Timothée Mazzucotelli).

v0.18.0

Compare Source

Compare with 0.17.0

Highlights
Packaging / Dependencies
  • Add Crystal extra, update Python extras versions (b8222b0 by Timothée Mazzucotelli). PR #​374
  • Update autorefs to actually required version (fc6c7f6 by Timothée Mazzucotelli).
  • Drop Python 3.6 support (7205ac6 by Timothée Mazzucotelli).
Features
  • Allow unwrapping the <p> tag in convert_markdown filter (5351fc8 by Oleh Prypin). PR #​369
  • Support handlers spanning multiple locations (f42dfc6 by Timothée Mazzucotelli). PR #​355
Code Refactoring

v0.17.0

Compare Source

Compare with 0.16.2

Features
Bug Fixes
Code Refactoring

v0.16.2

Compare Source

Compare with 0.16.1

Dependencies
  • Support pymdown-extensions v9.x (0831343 by Ofek Lev and 38b22ec by Timothée Mazzucotelli).

v0.16.1

Compare Source

Compare with 0.16.0

Bug Fixes
  • Fix ReadTheDocs "return" template (598621b by Timothée Mazzucotelli).

v0.16.0

Compare Source

Compare with 0.15.0

Features
Bug Fixes
Code Refactoring
  • Move writing extra files to an earlier stage in the build (3890ab5 by Oleh Prypin). PR #​275

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

@renovate
Copy link
Author

renovate bot commented Feb 20, 2022

⚠ 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
Installing legacy tool poetry v1.1.13
The canonical source for Poetry's installation script is now https://install.python-poetry.org. Please update your usage to reflect this.
Retrieving Poetry metadata

# Welcome to Poetry!

This will download and install the latest version of Poetry,
a dependency and package manager for Python.

It will add the `poetry` command to Poetry's bin directory, located at:

/home/ubuntu/poetry/1.1.13/bin

You can uninstall at any time by executing this script with the --uninstall option,
and these changes will be reverted.

Installing Poetry (1.1.13)
Installing Poetry (1.1.13): Creating environment
Installing Poetry (1.1.13): Installing Poetry
Installing Poetry (1.1.13): Creating script
Installing Poetry (1.1.13): Done

Poetry (1.1.13) is installed now. Great!

To get started you need Poetry's bin directory (/home/ubuntu/poetry/1.1.13/bin) in your `PATH`
environment variable.

Add `export PATH="/home/ubuntu/poetry/1.1.13/bin:$PATH"` to your shell configuration file.

Alternatively, you can call Poetry explicitly with `/home/ubuntu/poetry/1.1.13/bin/poetry`.

You can test that everything is set up by executing:

`poetry --version`

Poetry version 1.1.13
Creating virtualenv wizard-domaininfo-DWYoKLWw-py3.10 in /home/ubuntu/.cache/pypoetry/virtualenvs
Updating dependencies
Resolving dependencies...

  SolverProblemError

  The current project's Python requirement (>=3.6.1,<4.0.0) is not compatible with some of the required packages Python requirement:
    - mkdocstrings requires Python >=3.7, so it will not be satisfied for Python >=3.6.1,<3.7
  
  Because mkdocstrings (0.19.0) requires Python >=3.7
   and no versions of mkdocstrings match >0.19.0,<0.20.0, mkdocstrings is forbidden.
  So, because wizard-domaininfo depends on mkdocstrings (^0.19.0), version solving failed.

  at ~/poetry/1.1.13/venv/lib/python3.10/site-packages/poetry/puzzle/solver.py:241 in _solve
      237│             packages = result.packages
      238│         except OverrideNeeded as e:
      239│             return self.solve_in_compatibility_mode(e.overrides, use_latest=use_latest)
      240│         except SolveFailure as e:
    → 241│             raise SolverProblemError(e)
      242│ 
      243│         results = dict(
      244│             depth_first_search(
      245│                 PackageNode(self._package, packages), aggregate_package_nodes

  • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties
    
    For mkdocstrings, a possible solution would be to set the `python` property to ">=3.7,<4.0.0"

    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
    https://python-poetry.org/docs/dependency-specification/#using-environment-markers


@renovate renovate bot force-pushed the renovate/mkdocstrings-0.x branch from a4252d2 to 7fb4fe0 Compare February 20, 2022 22:56
@renovate renovate bot force-pushed the renovate/mkdocstrings-0.x branch from 7fb4fe0 to 384cc3a Compare June 5, 2022 14:59
@renovate renovate bot changed the title chore(deps): update dependency mkdocstrings to ^0.18.0 chore(deps): update dependency mkdocstrings to ^0.19.0 Jun 5, 2022
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.

1 participant