-
-
Notifications
You must be signed in to change notification settings - Fork 183
Issues: conda-forge/conda-smithy
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
linter ignores selector when reporting duplicated keys
bug
#2161
opened Nov 23, 2024 by
njzjz
1 task done
getting python build matrix when python not in host
bug
#2156
opened Nov 21, 2024 by
minrk
1 task done
Linting
conda-forge.yml
does not diagnose (some) schema violations
#2152
opened Nov 21, 2024 by
h-vetinari
Add additional information to linter for noarch packages can't have skips with selectors
#2149
opened Nov 20, 2024 by
matthewfeickert
False positives in skip check (after merge on top of skipped commit)
#2139
opened Nov 18, 2024 by
h-vetinari
Consider adding pixi install commands to feedstock README template
question
#2127
opened Nov 9, 2024 by
matthewfeickert
conda smithy rerender -c auto
failing with AssertionError
on git repositories with index v3
bug
#2116
opened Nov 4, 2024 by
mgorny
1 task done
Support for nested conditionnal selectors in v2 recipe
question
#2109
opened Oct 30, 2024 by
olivier-roussel
improve conda linting message: No valid build backend found
bug
#2103
opened Oct 27, 2024 by
JohannesBuchner
1 task done
BUG: smithy 3.43.0 creates too many jobs on ctng-compiler-activation
#2100
opened Oct 21, 2024 by
h-vetinari
Linux: do not mount feedstock in CI to avoid cache copies, only locally
enhancement
#2098
opened Oct 17, 2024 by
jaimergp
use
--host-platform
instead of --target-platform
when calling rattler-build
#2072
opened Oct 1, 2024 by
beckermr
BUG:
ordering:
values in migrator not working when using additional_zip_keys
for that key
#2061
opened Sep 14, 2024 by
h-vetinari
Previous Next
ProTip!
Follow long discussions with comments:>50.