Skip to content

Commit

Permalink
Fix broken pyside6 constraint for napari 0.5.0 (#65)
Browse files Browse the repository at this point in the history
* dummy commit for rerendering

* address bad pyside6 constraint

* MNT: Re-rendered with conda-build 24.5.1, conda-smithy 3.36.2, and conda-forge-pinning 2024.07.15.21.42.37

* fix constraint again

* Update meta.yaml

---------

Co-authored-by: conda-forge-webservices[bot] <121827174+conda-forge-webservices[bot]@users.noreply.github.com>
Co-authored-by: Mark Harfouche <mark.harfouche@gmail.com>
Co-authored-by: conda-forge-webservices[bot] <91080706+conda-forge-webservices[bot]@users.noreply.github.com>
  • Loading branch information
4 people committed Jul 16, 2024
1 parent f29463f commit 149c206
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions recipe/meta.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ source:
sha256: 3920b144d72e8af8fe0da3da679b2d39aa2d097c10a2c75a3b4e42ffcef17cac

build:
number: 0
number: 1

outputs:
- name: napari
Expand Down Expand Up @@ -81,7 +81,7 @@ outputs:
run_constrained:
- napari-plugin-manager >=0.1.0a2,<0.3.0a0
- pyside2 >=5.13.2,!=5.15.0
- pyside6 <6.5,>=6.7
- pyside6 <6.5|>=6.7
- pyqt >=5.12.3,!=5.15.0,<6.0a0|>=6.5,!=6.6.1
# Nice for performance, but optional. Inclusion under discussion.
# - py-triangle
Expand Down

1 comment on commit 149c206

@conda-forge-webservices
Copy link
Contributor

Choose a reason for hiding this comment

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

Hi! This is the friendly automated conda-forge-webservice.

I updated the Github team because of this commit.

You should get push access to this feedstock and CI services.

Your package won't be available for installation locally until it is built
and synced to the anaconda.org CDN (takes 1-2 hours after the build finishes).

Feel free to join the community Element channel.

NOTE: Please make sure to not push to the repository directly.
Use branches in your fork for any changes and send a PR.
More details on this are here.

Please sign in to comment.