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 mkdocs-macros-plugin to ^0.7.0 #29

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jun 5, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
mkdocs-macros-plugin ^0.5.0 -> ^0.7.0 age adoption passing confidence

Release Notes

fralau/mkdocs_macros_plugin

v0.7.0

Compare Source

  • Added: (#​133) on_error_fail in config file to make build/serve process
    fail in case of macro error, with return code 100.

  • Added: (#​130) Documentation on the tree structure of a typical
    macro directory (package)

v0.6.4

Compare Source

  • Fixed: (#​118) {{ git.date }} is now committer date (no longer author date).
  • Added: new git info elements (author email, committer, committer email);
    documentation was updated
  • Added: by default, unknown variables in a markdown page ({{ foo }})
    are no longer replaced by blanks but displayed as is (DebugUndefined) (#​117);
    for better compatibility with other plugins or error detection
  • Added: on_undefined parameter in plugin definition to alter behavior
    with unknown jinja2 variables: 'keep' (default), 'silent', 'strict', 'lax';
    documentation was updated

v0.6.3

Compare Source

  • Fixed: Broken build of 0.6.2

v0.6.2

Compare Source

  • Added: env.raw_markdown is now modifiable, for use in on_post_page_macros()

v0.6.0

Compare Source

  • Fixed: documentation (for readthedocs) now contains proper
    link to edit uri on github
  • Fixed: broken link in webdoc/docs/pages.md
  • Bump version to 0.6.0, to acknowledge the breaking change in 0.5.10

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 Jun 5, 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:
    - git-changelog requires Python >=3.6.2, so it will not be satisfied for Python >=3.6.1,<3.6.2
  
  Because git-changelog (0.5.0) requires Python >=3.6.2
   and no versions of git-changelog match >0.5.0,<0.6.0, git-changelog is forbidden.
  So, because wizard-domaininfo depends on git-changelog (^0.5.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 git-changelog, a possible solution would be to set the `python` property to ">=3.6.2,<4.0.0"

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


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