chore(deps): update ampel packages

renovate[bot] commented 1 year ago

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
ampel-interface (source)	`>=0.8.7,<0.9` -> `>=0.10.1.post0,<0.11`
ampel-ztf (source)	`>=0.8.5,<0.9` -> `>=0.10.2,<0.11`

Release Notes

AmpelProject/Ampel-interface (ampel-interface)

### [`v0.10.1.post0`](https://redirect.github.com/AmpelProject/Ampel-interface/compare/v0.10.1...v0.10.1.post0) [Compare Source](https://redirect.github.com/AmpelProject/Ampel-interface/compare/v0.10.1...v0.10.1.post0) ### [`v0.10.1`](https://redirect.github.com/AmpelProject/Ampel-interface/compare/v0.10.0...v0.10.1) [Compare Source](https://redirect.github.com/AmpelProject/Ampel-interface/compare/v0.10.0...v0.10.1) ### [`v0.10.0`](https://redirect.github.com/AmpelProject/Ampel-interface/compare/v0.9.0...v0.10.0) [Compare Source](https://redirect.github.com/AmpelProject/Ampel-interface/compare/v0.9.0...v0.10.0) ### [`v0.9.0`](https://redirect.github.com/AmpelProject/Ampel-interface/compare/v0.8.12...v0.9.0) [Compare Source](https://redirect.github.com/AmpelProject/Ampel-interface/compare/v0.8.12...v0.9.0)

AmpelProject/Ampel-ZTF (ampel-ztf)

### [`v0.10.2`](https://redirect.github.com/AmpelProject/Ampel-ZTF/compare/v0.10.0...v0.10.2) [Compare Source](https://redirect.github.com/AmpelProject/Ampel-ZTF/compare/v0.10.0...v0.10.2) ### [`v0.10.0`](https://redirect.github.com/AmpelProject/Ampel-ZTF/compare/v0.9.0...v0.10.0) [Compare Source](https://redirect.github.com/AmpelProject/Ampel-ZTF/compare/v0.9.0...v0.10.0) ### [`v0.9.0`](https://redirect.github.com/AmpelProject/Ampel-ZTF/compare/v0.8.16...v0.9.0) [Compare Source](https://redirect.github.com/AmpelProject/Ampel-ZTF/compare/v0.8.16...v0.9.0) ### [`v0.8.16`](https://redirect.github.com/AmpelProject/Ampel-ZTF/compare/v0.8.15...v0.8.16) [Compare Source](https://redirect.github.com/AmpelProject/Ampel-ZTF/compare/v0.8.15...v0.8.16)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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[bot] commented 1 year ago

⚠ 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 ampel-nuclear-FsBIphGQ-py3.11 in /home/ubuntu/.cache/pypoetry/virtualenvs

The current project's Python requirement (>=3.10,<3.12) is not compatible with some of the required packages Python requirement:
  - ampel-hu-astro requires Python >=3.10,<3.11, so it will not be satisfied for Python >=3.11,<3.12
  - ampel-hu-astro requires Python >=3.10,<3.11, so it will not be satisfied for Python >=3.11,<3.12
  - ampel-hu-astro requires Python >=3.10,<3.11, so it will not be satisfied for Python >=3.11,<3.12
  - ampel-hu-astro requires Python >=3.10,<3.11, so it will not be satisfied for Python >=3.11,<3.12
  - ampel-hu-astro requires Python >=3.10,<3.11, so it will not be satisfied for Python >=3.11,<3.12

Because no versions of ampel-hu-astro match >0.8.3a10,<0.8.3a11 || >0.8.3a11,<0.8.3a12 || >0.8.3a12,<0.8.3a13 || >0.8.3a13,<0.8.3a14 || >0.8.3a14,<0.8.3a15 || >0.8.3a15,<0.8.3a16 || >0.8.3a16,<0.8.3a18 || >0.8.3a18,<0.8.3a19 || >0.8.3a19,<0.8.3a20 || >0.8.3a20,<0.8.4
 and ampel-hu-astro (0.8.3a10) requires Python >=3.10,<3.11, ampel-hu-astro is forbidden.
And because ampel-hu-astro (0.8.3a11) requires Python >=3.10,<3.11
 and ampel-hu-astro (0.8.3a12) requires Python >=3.10,<3.11, ampel-hu-astro is forbidden.
And because ampel-hu-astro (0.8.3a13) requires Python >=3.10,<3.11
 and ampel-hu-astro (0.8.3a14) requires Python >=3.10,<3.11, ampel-hu-astro is forbidden.
And because ampel-hu-astro (0.8.3a15) depends on ampel-photometry (>=0.8.3,<0.9.0)
 and ampel-hu-astro (0.8.3a16) depends on ampel-photometry (>=0.8.3,<0.9.0), ampel-hu-astro (>=0.8.3a10,<0.8.3a18 || >0.8.3a18,<0.8.3a19 || >0.8.3a19,<0.8.3a20 || >0.8.3a20,<0.8.4) requires ampel-photometry (>=0.8.3,<0.9.0).
And because ampel-hu-astro (0.8.3a18) depends on ampel-photometry (>=0.8.3,<0.9.0)
 and ampel-hu-astro (0.8.3a19) depends on ampel-interface (>=0.8.5,<0.9.0), ampel-hu-astro (>=0.8.3a10,<0.8.3a20 || >0.8.3a20,<0.8.4) requires ampel-interface (>=0.8.5,<0.9.0) or ampel-photometry (>=0.8.3,<0.9.0).
Because no versions of ampel-ztf match >0.10.0,<0.10.1
 and ampel-ztf (0.10.0) depends on ampel-photometry (>=0.10.0a0,<0.11), ampel-ztf (>=0.10.0,<0.10.1) requires ampel-photometry (>=0.10.0a0,<0.11).
Thus, if ampel-ztf (>=0.10.0,<0.10.1) and ampel-hu-astro (>=0.8.3a10,<0.8.3a20 || >0.8.3a20,<0.8.4) then ampel-interface (>=0.8.5,<0.9.0).
And because ampel-hu-astro (0.8.3a20) depends on ampel-interface (>=0.8.7,<0.9.0)
 and ampel-nuclear depends on ampel-interface (^0.10.0), ampel-ztf (>=0.10.0,<0.10.1) is incompatible with ampel-hu-astro (>=0.8.3a10,<0.8.4).
So, because ampel-nuclear depends on both ampel-hu-astro (>=0.8.3a10,<0.8.4) and ampel-ztf (>=0.10.0,<0.10.1), version solving failed.

  • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties

    For ampel-hu-astro, a possible solution would be to set the `python` property to ">=3.10,<3.11"
    For ampel-hu-astro, a possible solution would be to set the `python` property to ">=3.10,<3.11"
    For ampel-hu-astro, a possible solution would be to set the `python` property to ">=3.10,<3.11"
    For ampel-hu-astro, a possible solution would be to set the `python` property to ">=3.10,<3.11"
    For ampel-hu-astro, a possible solution would be to set the `python` property to ">=3.10,<3.11"

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

renovate[bot] commented 5 months ago

⚠️ 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 ampel-nuclear-FsBIphGQ-py3.11 in /home/ubuntu/.cache/pypoetry/virtualenvs

The current project's supported Python range (>=3.10,<3.12) is not compatible with some of the required packages Python requirement:
  - ampel-hu-astro requires Python >=3.10,<3.11, so it will not be satisfied for Python >=3.11,<3.12
  - ampel-hu-astro requires Python >=3.10,<3.11, so it will not be satisfied for Python >=3.11,<3.12
  - ampel-hu-astro requires Python >=3.10,<3.11, so it will not be satisfied for Python >=3.11,<3.12
  - ampel-hu-astro requires Python >=3.10,<3.11, so it will not be satisfied for Python >=3.11,<3.12
  - ampel-hu-astro requires Python >=3.10,<3.11, so it will not be satisfied for Python >=3.11,<3.12

Because no versions of ampel-hu-astro match >0.8.3a10,<0.8.3a11 || >0.8.3a11,<0.8.3a12 || >0.8.3a12,<0.8.3a13 || >0.8.3a13,<0.8.3a14 || >0.8.3a14,<0.8.3a15 || >0.8.3a15,<0.8.3a16 || >0.8.3a16,<0.8.3a18 || >0.8.3a18,<0.8.3a19 || >0.8.3a19,<0.8.3a20 || >0.8.3a20,<0.8.4a0 || >0.8.4a0,<0.8.4a1 || >0.8.4a1,<0.8.4a2 || >0.8.4a2,<0.8.4a3 || >0.8.4a3,<0.8.4a4 || >0.8.4a4,<0.9
 and ampel-hu-astro[slack,sncosmo] (0.8.3a10) requires Python >=3.10,<3.11, ampel-hu-astro is forbidden.
And because ampel-hu-astro[slack,sncosmo] (0.8.3a11) requires Python >=3.10,<3.11
 and ampel-hu-astro[slack,sncosmo] (0.8.3a12) requires Python >=3.10,<3.11, ampel-hu-astro is forbidden.
And because ampel-hu-astro[slack,sncosmo] (0.8.3a13) requires Python >=3.10,<3.11
 and ampel-hu-astro[slack,sncosmo] (0.8.3a14) requires Python >=3.10,<3.11, ampel-hu-astro is forbidden.
And because ampel-hu-astro[slack,sncosmo] (0.8.3a15) depends on ampel-photometry (>=0.8.3,<0.9.0)
 and ampel-hu-astro[slack,sncosmo] (0.8.3a16) depends on ampel-photometry (>=0.8.3,<0.9.0), ampel-hu-astro[slack,sncosmo] (>=0.8.3a10,<0.8.3a18 || >0.8.3a18,<0.8.3a19 || >0.8.3a19,<0.8.3a20 || >0.8.3a20,<0.8.4a0 || >0.8.4a0,<0.8.4a1 || >0.8.4a1,<0.8.4a2 || >0.8.4a2,<0.8.4a3 || >0.8.4a3,<0.8.4a4 || >0.8.4a4,<0.9) requires ampel-photometry (>=0.8.3,<0.9.0).
And because ampel-hu-astro[slack,sncosmo] (0.8.3a18) depends on ampel-photometry (>=0.8.3,<0.9.0)
 and ampel-hu-astro[slack,sncosmo] (0.8.3a19) depends on ampel-interface (>=0.8.5,<0.9.0), ampel-hu-astro[slack,sncosmo] (>=0.8.3a10,<0.8.3a20 || >0.8.3a20,<0.8.4a0 || >0.8.4a0,<0.8.4a1 || >0.8.4a1,<0.8.4a2 || >0.8.4a2,<0.8.4a3 || >0.8.4a3,<0.8.4a4 || >0.8.4a4,<0.9) requires ampel-photometry (>=0.8.3,<0.9.0) or ampel-interface (>=0.8.5,<0.9.0).
And because ampel-hu-astro[slack,sncosmo] (0.8.3a20) depends on ampel-interface (>=0.8.7,<0.9.0)
 and ampel-hu-astro[slack,sncosmo] (0.8.4a0) depends on ampel-alerts (>=0.8.5,<0.9), ampel-hu-astro[slack,sncosmo] (>=0.8.3a10,<0.8.4a1 || >0.8.4a1,<0.8.4a2 || >0.8.4a2,<0.8.4a3 || >0.8.4a3,<0.8.4a4 || >0.8.4a4,<0.9) requires ampel-photometry (>=0.8.3,<0.9.0) or ampel-interface (>=0.8.5,<0.9.0) or ampel-alerts (>=0.8.5,<0.9).
And because ampel-hu-astro[slack,sncosmo] (0.8.4a2) depends on ampel-alerts (>=0.8.5,<0.9)
 and ampel-hu-astro[slack,sncosmo] (0.8.4a3) depends on ampel-alerts (>=0.8.5,<0.9), ampel-hu-astro[slack,sncosmo] (>=0.8.3a10,<0.8.4a1 || >0.8.4a1,<0.8.4a4 || >0.8.4a4,<0.9) requires ampel-photometry (>=0.8.3,<0.9.0) or ampel-interface (>=0.8.5,<0.9.0) or ampel-alerts (>=0.8.5,<0.9).
And because ampel-hu-astro[slack,sncosmo] (0.8.4a4) depends on ampel-alerts (>=0.8.5,<0.9)
 and ampel-hu-astro[slack,sncosmo] (0.8.4a1) depends on ampel-alerts (>=0.8.5,<0.9), ampel-hu-astro[slack,sncosmo] (>=0.8.3a10,<0.9) requires ampel-alerts (>=0.8.5,<0.9) or ampel-photometry (>=0.8.3,<0.9.0) or ampel-interface (>=0.8.5,<0.9.0).
And because ampel-ztf (0.10.2) depends on both ampel-alerts (>=0.10.1,<0.11) and ampel-photometry (>=0.10.0a0,<0.11), if ampel-hu-astro[slack,sncosmo] (>=0.8.3a10,<0.9) and ampel-ztf (0.10.2) then ampel-interface (>=0.8.5,<0.9.0).
And because no versions of ampel-ztf match >0.10.2,<0.11
 and ampel-nuclear depends on ampel-interface (>=0.10.1.post0,<0.11), ampel-hu-astro[slack,sncosmo] (>=0.8.3a10,<0.9) is incompatible with ampel-ztf (>=0.10.2,<0.11).
So, because ampel-nuclear depends on both ampel-ztf (>=0.10.2,<0.11) and ampel-hu-astro[slack,sncosmo] (>=0.8.3a10,<0.9), version solving failed.

  • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties

    For ampel-hu-astro, a possible solution would be to set the `python` property to ">=3.10,<3.11"
    For ampel-hu-astro, a possible solution would be to set the `python` property to ">=3.10,<3.11"
    For ampel-hu-astro, a possible solution would be to set the `python` property to ">=3.10,<3.11"
    For ampel-hu-astro, a possible solution would be to set the `python` property to ">=3.10,<3.11"
    For ampel-hu-astro, a possible solution would be to set the `python` property to ">=3.10,<3.11"

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

AmpelAstro / Ampel-nuclear