Validate package names against CEP-26 naming conventions - #5977
Open
jezdez wants to merge 1 commit into
Open
Conversation
conda-bot
added
the
cla-signed
jezdez
marked this pull request as ready for review
July 22, 2026 09:24
Add check_package_name() that validates package/name against the CEP-26 distributable and virtual package name regexes, replacing the generic check_bad_chrs() call for package names.
jezdez
force-pushed
the
fix/cep26-package-name-validation
branch
from
July 22, 2026 09:25
312526e to
aa6bdc2
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Validates
package/namein recipes against CEP-26 naming conventions, matching the validation recently added to conda's MatchSpec parser (conda/conda#16096).Adds a
check_package_name()function with the CEP-26 distributable and virtual package name regexes. This replaces the genericcheck_bad_chrs()call forpackage/name(which only checked a hardcoded set of special characters) with proper structural validation:[a-z0-9]or single_, use only[a-z0-9._-], no consecutive separators__, followed by valid name characterscheck_bad_chrs()continues to servepackage/versionandbuild/stringfields unchanged.Closes #5976.
Checklist - did you ...
newsdirectory (using the template) for the next release's release notes?Add / update outdated documentation?(not applicable)