* Fix pip package name matching in downgrade guards * Apply the pip blacklists however a requirement is written Build on the name normalization to close the other ways a listed requirement escaped the pip_blacklist and downgrade_blacklist checks. - Parse requirements with packaging and share one parser and one downgrade decision between both cores, the startup check and the unified resolver - Treat '-', '_' and '.' as one separator in package names - Read every version clause, so a lower bound written first no longer hides an upper bound; read spaces, parentheses, markers, '===' and direct references; compare local and four-part versions - Install a requirement with extras unless it would downgrade the protected package - Check the requirement of every pip install command form, including those with --index-url, on the immediate and reserved paths - Skip a protected package when the requirement cannot be compared and log why and how to install it - At startup, recognize an installed package however its requirement spells the name, and upgrade one older than its '~=' version - Remove the unused is_installed copies from both cores - Add regression tests; update README, CHANGELOG and the resolver design --------- Co-authored-by: Annika Zhang <287326049+annikazhang77@users.noreply.github.com> Co-authored-by: Dr.Lt.Data <dr.lt.data@gmail.com>
ComfyUI-Manager: Documentation
This directory contains documentation for the ComfyUI-Manager, providing guides and tutorials for users in multiple languages.
Directory Structure
The documentation is organized into language-specific directories:
- en/: English documentation
- ko/: Korean documentation
Core Documentation Files
Command-Line Interface
- cm-cli.md: Documentation for the ComfyUI-Manager Command Line Interface (CLI), which allows using manager functionality without the UI.
Advanced Features
- use_aria2.md: Guide for using the aria2 download accelerator with ComfyUI-Manager for faster model downloads.
Documentation Standards
The documentation follows these standards:
- Markdown Format: All documentation is written in Markdown for easy rendering on GitHub and other platforms
- Language-specific Directories: Content is separated by language to facilitate localization
- Feature-focused Documentation: Each major feature has its own documentation file
- Updated with Releases: Documentation is kept in sync with software releases
Contributing to Documentation
When contributing new documentation:
- Place files in the appropriate language directory
- Use clear, concise language appropriate for the target audience
- Include examples where helpful
- Consider adding screenshots or diagrams for complex features
- Maintain consistent formatting with existing documentation
This documentation directory will continue to grow to support the expanding feature set of ComfyUI-Manager.