v0.8.40 + conda-forge.yml modernization by rxm7706 · Pull Request #8 · conda-forge/graphifyy-feedstock

rxm7706 · 2026-06-16T23:34:10Z

Bump graphifyy 0.8.10 → 0.8.40 (30 versions; supersedes 4 stale autotick PRs that were just closed) and modernize conda-forge.yml to the 2026 canonical shape.

Recipe changes (v0.8.40)

+ numpy >=1.21 — new in v0.8.40 per upstream pyproject.toml
− datasketch — removed by upstream
All tree-sitter- run-deps now version-pinned* to match upstream's declared bounds
yaml-language-server schema header added (local-recipes convention; optional in conda-forge generally)
recipe-maintainers ordered alphabetically (killua156, mgorny, rxm7706)

`conda-forge.yml` modernization

+ conda_install_tool: pixi — faster than micromamba; matches conda-forge's 2026 standardization
bot: block extended with inspection: update-grayskull, check_solvable, run_deps_from_wheel (preserves existing automerge: true)
Intentionally omits the provider: / build_platform: / test: native_and_emulated block we shipped on the 22 tree-sitter-* platform-expansion PRs this session — graphifyy is noarch: python, so a single linux-64 build serves all subdirs automatically.

Local verification

validate:      [OK]   schema_version: 1, conda-smithy lint passed
lint-optimize: [OK]   0 suggestions
check-deps:    [OK]   29/29 run-deps resolve on conda-forge

Context

This PR closes out the 2026-06-16 osx-arm64 enablement session — the 22 tree-sitter-* platform-expansion PRs merged earlier today now ship osx-arm64 artifacts; once those propagate to repodata (~1-6 h post-merge), graphifyy on osx-arm64 becomes installable. Spec: docs/specs/graphifyy-osx-arm64-fanout.md.

DRAFT until reviewer-confirms — happy to flip to ready when convenient.

Bump v0.8.10 -> v0.8.40 (30 versions; 4 stale autotick PRs closed in favor of this direct bump). Updates: - run-deps: + numpy>=1.21 (new in v0.8.40); - datasketch (removed upstream); all tree-sitter-* run-deps now carry the version pins declared in upstream's pyproject.toml [project.dependencies] - schema header (yaml-language-server) added per local convention - recipe-maintainers ordered alphabetically (killua156, mgorny, rxm7706) conda-forge.yml modernized to the 2026 canonical shape: - + conda_install_tool: pixi (faster than micromamba; matches conda-forge's 2026 standardization) - bot block extended with `inspection: update-grayskull`, `check_solvable`, `run_deps_from_wheel` (preserves existing `automerge: true`) Note: graphifyy is noarch:python, so the platform-expansion block (provider/build_platform/test) used on the 22 tree-sitter-* platform-expansion PRs is intentionally OMITTED here — noarch packages build once and ship to all subdirs. Verified locally: validate + check-deps + lint-optimize all clean; 29/29 run-deps resolve on conda-forge. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

rxm7706 · 2026-06-16T23:34:11Z

@conda-forge-admin, please rerender

conda-forge-admin · 2026-06-16T23:35:43Z

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/recipe.yaml) and found it was in an excellent condition.

…2026.06.16.09.36.5

rxm7706 · 2026-06-16T23:39:28Z

@conda-forge-admin, please rerender

Per CFE optimizer DEP-002 guidance and conda-forge convention for non-speculative shape: keep lower bounds (load-bearing minimum versions) and let the conda solver handle compatibility. Drops the upstream-declared `<X` upper bounds that pip would respect but conda-forge generally treats as advisory. Net effect: simpler recipe, less churn on every dep version bump (bot.run_deps_from_wheel still extracts lower bounds correctly). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

conda-forge-admin · 2026-06-16T23:41:26Z

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

I tried to rerender for you, but it looks like there was nothing to do.

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

Two corrections: (1) `tree-sitter >=0.23.0` -> `tree_sitter >=0.23.0` for the core tree-sitter dep. conda-forge ships the core under the underscore-preserved name `tree_sitter` (109 builds on linux-64); the hyphenated `tree-sitter-X.Y.Z` namespace is used only by the language bindings (456 builds, all of which correctly used hyphens in the recipe). Underscore-preserved core is the documented form per CFE SKILL.md G10 + feedback_pypi_conda_mapping_unreliable.md memory entry. (2) Restore the `script: graphify --help` test (with `pip` in requirements.run) that the local mirror carried. Catches CLI entry-point breakage at test time — particularly meaningful after the upper-bound drop, since pip_check alone covers declared-dep version conflicts but not entry-point / runtime breakage. Main feedstock didn't have it (dropped via an earlier PR I think); restoring is a net-positive safety net. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

rxm7706 · 2026-06-16T23:46:48Z

@conda-forge-admin, please rerender

conda-forge-admin · 2026-06-16T23:48:41Z

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

I tried to rerender for you, but it looks like there was nothing to do.

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

Upstream's [project.optional-dependencies] defines `sql = ["tree-sitter-sql"]`. run_constrained is the conda-forge canonical pattern for soft / optional deps: graphifyy alone does not pull in tree-sitter-sql; when the user installs both, conda guarantees compatible versions. Lower bound (>=0.3) matches tree-sitter-sql's tested-with floor on conda-forge (latest 0.3.11). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

rxm7706 · 2026-06-16T23:54:28Z

@conda-forge-admin, please rerender

conda-forge-admin · 2026-06-16T23:56:35Z

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

I tried to rerender for you but ran into some issues. Please check the output logs of the GitHub Actions workflow below for more details. You can also ping conda-forge/core (using the @ notation) for further assistance or you can try rerendering locally.

The following suggestions might help debug any issues:

Is the recipe/{meta.yaml,recipe.yaml} file valid?
If there is a recipe/conda-build-config.yaml file in the feedstock make sure that it is compatible with the current global pinnings.
Is the fork used for this PR on an organization or user GitHub account? Automated rerendering via the webservices admin bot only works for user GitHub accounts.

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

Adds 16 more soft constraints covering upstream's [project.optional-dependencies] groups whose deps are available on conda-forge across all platforms we ship (linux-64, osx-64, win-64, osx-arm64, linux-aarch64, linux-ppc64le): - mcp, anthropic, openai, tiktoken, boto3 (LLM backends: mcp/anthropic/openai/kimi/ollama/gemini/bedrock) - neo4j-python-driver (neo4j extra; PyPI `neo4j` -> conda-forge rename per G10 / SKILL.md) - pypdf, markdownify (pdf extra) - watchdog (watch extra) - matplotlib (svg extra) - graspologic (leiden extra) - python-docx, openpyxl (office + google extras) - psycopg (postgres extra; conda-forge psycopg includes the `[binary]` backend by default) - yt-dlp (video extra; faster-whisper omitted - see below) - jieba (chinese extra) Intentionally omitted (not yet on conda-forge): - falkordb (falkordb extra) - faster-whisper (video extra) run_constrained semantics keep graphifyy lean by default - none of these are pulled in on `mamba install graphifyy`. Users opt in explicitly: `mamba install graphifyy openai tiktoken mcp`. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

rxm7706 · 2026-06-16T23:58:51Z

@conda-forge-admin, please rerender

conda-forge-admin · 2026-06-17T00:00:45Z

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

I tried to rerender for you but ran into some issues. Please check the output logs of the GitHub Actions workflow below for more details. You can also ping conda-forge/core (using the @ notation) for further assistance or you can try rerendering locally.

The following suggestions might help debug any issues:

Is the recipe/{meta.yaml,recipe.yaml} file valid?
If there is a recipe/conda-build-config.yaml file in the feedstock make sure that it is compatible with the current global pinnings.
Is the fork used for this PR on an organization or user GitHub account? Automated rerendering via the webservices admin bot only works for user GitHub accounts.

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

Updated dependency constraints and removed optional comments.

rxm7706 · 2026-06-17T00:51:40Z

@conda-forge-admin, please rerender

conda-forge-admin · 2026-06-17T00:53:28Z

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

I tried to rerender for you, but it looks like there was nothing to do.

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

Updated version constraints for tree-sitter packages and added run requirements for pip.

…1 -> 0.7.3 Upstream alex-pinkus/tree-sitter-swift has never bumped its pyproject.toml `version` field from the placeholder `0.0.1` despite tagging releases up through v0.7.3 — the tag scheme is the only source-of-truth for the actual grammar version. PyPI's `tree-sitter-swift` is stuck at v0.0.1 for the same reason; this feedstock has been shipping with the conda label `0.7.3` but the embedded dist-info metadata says `0.0.1`. Downstream impact: `pip check` against any package that declares `tree-sitter-swift>=0.7,<0.9` (e.g. graphifyy v0.8.40 in conda-forge/graphifyy-feedstock#8) fails — conda picks our 0.7.3 package, but pip then reads the wheel-bundled dist-info's 0.0.1 < 0.7 and rejects it. Two-part fix: 1. Bump tag `0.7.2-with-generated-files` -> `0.7.3-with-generated-files` (was lazy-labeled as 0.7.3 in conda while sourcing 0.7.2). New sha256: e2e84d3b97cf6a0afbcab793c4910123da92a34c395b09cc8d0880562a21e956 2. Add patches/0001-bump-pyproject-version-to-match-tag.patch which rewrites `version = "0.0.1"` -> `version = "0.7.3"` in pyproject.toml at build time. Build number bumped 1 -> 2 (same-version recipe-shape change supersedes existing *_1 artifacts). This patch becomes a no-op once upstream restores version-bumping discipline. Filing upstream issue in a follow-up. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

rxm7706 · 2026-06-17T02:21:46Z

@conda-forge-admin, please rerender

conda-forge-admin · 2026-06-17T02:23:46Z

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

I tried to rerender for you, but it looks like there was nothing to do.

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

rxm7706 · 2026-06-17T02:57:10Z

@conda-forge-admin, please restart ci

rxm7706 · 2026-06-17T02:57:35Z

@conda-forge-admin, please rerender

conda-forge-admin · 2026-06-17T02:59:39Z

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

I tried to rerender for you, but it looks like there was nothing to do.

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

conda-forge-admin · 2026-06-17T02:59:50Z

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

I tried to rerender for you, but it looks like there was nothing to do.

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

MNT: Re-rendered with conda-smithy 2026.6.14 and conda-forge-pinning …

f0db83d

…2026.06.16.09.36.5

Refactor dependency constraints in recipe.yaml

1152198

Updated dependency constraints and removed optional comments.

Refine tree-sitter package version constraints

3227888

Updated version constraints for tree-sitter packages and added run requirements for pip.

conda-forge-webservices Bot closed this Jun 17, 2026

conda-forge-webservices Bot reopened this Jun 17, 2026

rxm7706 marked this pull request as ready for review June 17, 2026 02:57

rxm7706 requested review from killua156 and mgorny as code owners June 17, 2026 02:57

rxm7706 merged commit fa094fa into conda-forge:main Jun 17, 2026
3 of 4 checks passed

Uh oh!

Conversation

rxm7706 commented Jun 16, 2026

Recipe changes (v0.8.40)

conda-forge.yml modernization

Local verification

Context

Uh oh!

rxm7706 commented Jun 16, 2026

Uh oh!

conda-forge-admin commented Jun 16, 2026

Uh oh!

rxm7706 commented Jun 16, 2026

Uh oh!

conda-forge-admin commented Jun 16, 2026

Uh oh!

rxm7706 commented Jun 16, 2026

Uh oh!

conda-forge-admin commented Jun 16, 2026

Uh oh!

rxm7706 commented Jun 16, 2026

Uh oh!

conda-forge-admin commented Jun 16, 2026

Uh oh!

rxm7706 commented Jun 16, 2026

Uh oh!

conda-forge-admin commented Jun 17, 2026

Uh oh!

rxm7706 commented Jun 17, 2026

Uh oh!

conda-forge-admin commented Jun 17, 2026

Uh oh!

rxm7706 commented Jun 17, 2026

Uh oh!

conda-forge-admin commented Jun 17, 2026

Uh oh!

rxm7706 commented Jun 17, 2026

Uh oh!

rxm7706 commented Jun 17, 2026

Uh oh!

conda-forge-admin commented Jun 17, 2026

Uh oh!

conda-forge-admin commented Jun 17, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

`conda-forge.yml` modernization