conda bot is not pushing any new versions automatically

[geoHeil]

Solution to issue cannot be found in the documentation.

• I checked the documentation.

Issue

I am maintaining https://github.com/conda-forge/dagster-cloud-cli-feedstock and https://github.com/conda-forge/dagster-cloud-feedstock the first one is updating fine via the bot automation - however, the 2nd one seems to be stuck at 1.7.12 (roughly 1 month ago) - current version would be 1.8.0 what am I doing wrong - why is the bot not firing for the 2nd project both yml files https://github.com/conda-forge/dagster-cloud-feedstock/blob/main/conda-forge.yml look pretty identical

I just ran a #3 manual PR/update to 1.8.0

and the diff for the bot config compared to the working one is 0

Installed packages

bot is not triggering

bot:
    # only automerge on successful version PRs, migrations are not automerged
    automerge: 'version'
    # only open PRs if resulting environment is solvable, useful for tightly coupled packages
    check_solvable: true
    inspection: update-all

Environment info

not applicable

[geoHeil]

@conda-forge/core Could you please take a look at this issue?

[xhochy]

It's not solvable, see https://conda-forge.org/status/ -> Errored Version Updates.

[geoHeil]

linking our discussion over https://matrix.to/#/!SOyumkgPRWoXfQYIFH:matrix.org/$172346237810TuzpF:gitter.im?via=matrix.org&via=gitter.im&via=matrix.lmu.de

1234567891011121314151617181920212223                linux_64_: Cannot solve the request because of: dagster_gcp * cannot be installed because there are no viable options:
└─ dagster_gcp 0.6.5 would require
   └─ dagster_pandas *, which cannot be installed because there are no viable options:
      ├─ dagster_pandas 0.6.7.post0 would require
      │  └─ dagster 0.6.7.post0.*, which cannot be installed because there are no viable options:
      │     └─ dagster 0.6.7.post0 | 0.6.7.post0 | 0.6.7.post0 | 0.6.7.post0 would require
      │        └─ enum-compat >=0.0.1, for which no candidates were found.
      ├─ dagster_pandas 0.6.7 would require
      │  └─ dagster 0.6.7.*, which cannot be installed because there are no viable options:
      │     └─ dagster 0.6.7 | 0.6.7 | 0.6.7 | 0.6.7 would require
      │        └─ enum-compat >=0.0.1, for which no candidates were found.
      ├─ dagster_pandas 0.6.6 would require
      │  └─ dagster 0.6.6.*, which cannot be installed because there are no viable options:
      │     └─ dagster 0.6.6 | 0.6.6 | 0.6.6 | 0.6.6 would require
      │        └─ enum-compat >=0.0.1, for which no candidates were found.
      ├─ dagster_pandas 0.6.5 would require
      │  └─ dagster 0.6.5.*, which cannot be installed because there are no viable options:
      │     └─ dagster 0.6.5 | 0.6.5 | 0.6.5 | 0.6.5 would require
      │        └─ enum-compat >=0.0.1, for which no candidates were found.
      └─ dagster_pandas 0.6.4 would require
         └─ dagster 0.6.4.*, which cannot be installed because there are no viable options:
            └─ dagster 0.6.4 | 0.6.4 | 0.6.4 would require
               └─ enum-compat >=0.0.1, for which no candidates were found.

dagster gcp is pulled in - bit it should not be

[geoHeil]

Would https://github.com/conda-forge/dagster-cloud-feedstock/blob/main/conda-forge.yml#L11 disabling check_solvable: true make any sense here?

[geoHeil]

there was the suggestion to switch from update-all to hint-all - but this would break the automerge as far as I understand

[geoHeil]

Automerge will happen if all CI checks pass. If no dependency updates are needed, that will happen with no intervention even without update-all. If updates are needed, the PR will initially fail and the maintainers will have to do the updates (adding new dependencies, updating pins, ...), but even in that case the automerge will then happen once the CI passes, so that one does not have to hang around just to wait for the CI to pass and then click "merge".

was a reply -- so I was wrong

[geoHeil]

hopefully #8 will fix this