Skip to content

constantly 23.10.4 + add killua156 as maintainer#6

Open
killua156 wants to merge 3 commits into
conda-forge:mainfrom
killua156:add-maintainer-23.10.4
Open

constantly 23.10.4 + add killua156 as maintainer#6
killua156 wants to merge 3 commits into
conda-forge:mainfrom
killua156:add-maintainer-23.10.4

Conversation

@killua156

@killua156 killua156 commented Jul 2, 2026

Copy link
Copy Markdown

Updates constantly to 23.10.4 and adds killua156 to recipe-maintainers.
This carries the same recipe changes as #4 (the autotick-bot bump)
and additionally adds a new maintainer, which is myself because

Supersedes #4.

Bumps constantly from 15.1.0 to 23.10.4 (same recipe changes as conda-forge#4:
pip-based build, python >=3.8, versioneer/setuptools host deps, pip
check test) and adds killua156 to recipe-maintainers.
@conda-forge-admin

conda-forge-admin commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe/recipe.yaml) and found some lint.

Here's what I've got...

For recipe/recipe.yaml:

  • ❌ The feedstock has no .ci_support files and thus will not build any packages.

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

Converts meta.yaml to the v1 recipe.yaml format, uses python_min pins
and pypi.org source url per linter hints, and sets conda_build_tool:
rattler-build. Keeps the 23.10.4 bump and the new killua156 maintainer.
@killua156

Copy link
Copy Markdown
Author

@conda-forge-admin, please rerender

@conda-forge-admin

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

@killua156

killua156 commented Jul 2, 2026

Copy link
Copy Markdown
Author

the constantly output is not registered in conda-forge/feedstock-outputs (outputs/c/o/n/constantly.json returns 404). This feedstock is stale (last built 15.1.0, never re-rendered) and predates the output-registration system, so validation cannot confirm this feedstock is allowed to produce constantly. This is unrelated to the recipe.

This can't be resolved from a fork PR (fork PRs have no feedstock token). It needs a maintainer to either:

  1. register the feedstock token so the output auto-registers (@conda-forge-admin, please add feedstock token), or
  2. merge this PR, after which the main-branch build runs with the token and auto-registers + uploads.

@isuruf / @conda-forge/core could you take a look? This PR also adds me as a maintainer. and Ive updated the recipe from meta.yaml to recipe.yaml

@xhochy

xhochy commented Jul 3, 2026

Copy link
Copy Markdown
Member

This can't be resolved from a fork PR (fork PRs have no feedstock token). It needs a maintainer to either:

  1. register the feedstock token so the output auto-registers (@conda-forge-admin, please add feedstock token), or
  2. merge this PR, after which the main-branch build runs with the token and auto-registers + uploads.

These statements are false, please make a PR to admin-requests to solve it.

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.

3 participants