Skip to content

Update for websockets=15#395

Open
azjps wants to merge 1 commit intoconda-forge:mainfrom
azjps:patch-1
Open

Update for websockets=15#395
azjps wants to merge 1 commit intoconda-forge:mainfrom
azjps:patch-1

Conversation

@azjps
Copy link

@azjps azjps commented Jul 16, 2025

The websockets version requirements were updated in PrefectHQ/prefect@79cb8b5 prefect==3.2.8, need to change the pinning of websockets here too (currently prefect conda can error for websockets==11 for example)

Closes #382

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

The websockets version requirements were updated in PrefectHQ/prefect@79cb8b5 `prefect==3.2.8`, need to change the pinning here too
@conda-forge-admin
Copy link
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

  • ℹ️ top-level output has some malformed specs:
  • In section run: aiosqlite >=0.17.0, <1.0.0, alembic >=1.7.5, <2.0.0, anyio >=4.4.0, <5.0.0, apprise >=1.1.0, <2.0.0, asgi-lifespan >=1.0, <3.0, asyncpg >=0.23, <1.0.0, cachetools >=5.3, <6.0, click >=8.0, <8.2, cloudpickle >=2.0, <4.0, coolname >=1.0.4, <3.0.0, croniter >=1.0.12, <5.0.0, dateparser >=1.1.1, <2.0.0, docker-py >=4.0, <8.0, fastapi >=0.111.0, <1.0.0, griffe >=0.49.0, <2.0.0, httpcore >=1.0.5, <2.0.0, httpx >=0.23, !=0.23.2, humanize >=4.9.0, <5.0.0, jinja2 >=3.0.0, <4.0.0, jsonpatch >=1.32, <2.0, jsonschema >=4.0.0, <5.0.0, opentelemetry-api >=1.27.0, <2.0, orjson >=3.7, <4.0, packaging >=21.3, <24.3, pendulum >=3.0.0, <4, pydantic >=2.7, <3.0.0, pydantic-core >=2.12.0, <3.0.0, pydantic-extra-types >=2.8.2, <3.0.0, python-slugify >=5.0, <9.0, python-dateutil >=2.8.2, <3.0.0, python-socks[asyncio] >=2.5.3, <3.0, pytz >=2021.1, <2025, pyyaml >=5.4.1, <7.0.0, readchar >=4.0.0, <5.0.0, rfc3339-validator >=0.1.4, <0.2.0, rich >=11.0, <14.0, sniffio >=1.3.0, <2.0.0, sqlalchemy[asyncio] >=2.0, <3.0.0, typer >=0.12.0,!= 0.12.2, <0.13.0, typing_extensions >=4.5.0, <5.0.0, ujson >=5.8.0, <6.0.0, websockets >=13.0, <16.0
    Requirement spec fields should match the syntax name [version [build]]to avoid known issues in conda-build. For example, instead of name =version=build, use name version.* build. There should be no spaces between version operators and versions either: python >= 3.8 should be python >=3.8.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/16332614550. Examine the logs at this URL for more detail.

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.

Websockets need to be above version 13

2 participants