-
-
Notifications
You must be signed in to change notification settings - Fork 274
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #2290 from conda-forge/outputs-no-reg
feat: add announcement of new output registration process
- Loading branch information
Showing
2 changed files
with
30 additions
and
13 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,11 @@ | ||
# Changes Feedstock Output Validation Procedure | ||
|
||
We have changed our feedstock output validation procedure. Instead of automatically | ||
adding new packages to existing feedstocks (e.g., when a new output is added), we will now | ||
require that maintainers submit a PR to add the new output via our | ||
[admin-requests repository](https://github.com/conda-forge/admin-requests?tab=readme-ov-file#add-a-package-output-to-a-feedstock). | ||
New feedstocks created via `staged-recipes` will have their outputs added automatically. If you maintain a feedstock | ||
that regularly adds new outputs (e.g., `llvmdev` has `libllvm18`, `libllvm19`, etc.), we have created a | ||
[list of feedstocks with allowed glob patterns](https://github.com/conda-forge/admin-requests/blob/main/.feedstock_outputs_autoreg_allowlist.yml). These feedstocks will have any outputs matching their glob patterns | ||
added automatically. If you would like to add your feedstock to this list, please submit a PR. Further | ||
details on package output validation cna be found in our [documentation](https://conda-forge.org/docs/maintainer/infrastructure/#output-validation-and-feedstock-tokens). |