Question: How to Publish Custom Node with Multiple Python Version Builds?

[K-O-N-B]

** Background
I'm developing a custom node that needs to support multiple Python versions (3.10, 3.11, 3.12, 3.13) due to platform-specific dependencies. Each Python version requires a separate build with compiled binaries.

** Current Situation
After reviewing the official documentation, I found that:

1. The pyproject.toml specification mentions requires-python for declaring supported Python versions, but it doesn't explicitly explain:
   1.1 How to handle multiple Python-specific builds
   1.2 Whether zip files need to be uploaded to GitHub Release
   1.3 What naming convention should be used for zip files (e.g., node-1.2.6-py310.zip, node-1.2.6-py311.zip)
   1.4 How the Registry backend selects the appropriate zip file based on the user's Python version

2.The documentation shows examples with a single version = "1.2.6" and requires-python = ">=3.8,<3.11", but doesn't cover the case where each Python version requires a separate build.

** What I've Tested
I've tried publishing separate versions with Python-specific suffixes:
version = "1.2.6-python310" with requires-python = ">=3.10,<3.11"
version = "1.2.6-python311" with requires-python = ">=3.11,<3.12"

Results:
✅ The Registry accepted these non-standard version numbers
✅ comfy node publish successfully uploaded files directly to Google Cloud Storage
✅ No GitHub Release was required (files were packaged from the current directory)
However, I'm unsure if this is the recommended approach or if there's a better way.

** Questions

1. Multiple Python Versions: What is the recommended way to publish a custom node that requires separate builds for different Python versions?
2. GitHub Release: Is it required to upload zip files to GitHub Release, or can comfy node publish package files directly from the local directory?
3. Zip File Naming: If multiple zip files are needed, is there a naming convention? For example:
   node-name-1.2.6-py310.zip
   node-name-1.2.6-py311.zip
   Or any other format?
4. Automatic Selection: How does the Registry backend select the appropriate zip file based on the user's Python version? Does it:
   4.1 Automatically detect from GitHub Release based on requires-python?
   4.2 Require users to manually select the version?
   4.3 Use some other mechanism?
5. Version Numbering: Is using version suffixes like 1.2.6-python310 acceptable, or should I use standard semantic versioning with a single version number?

**Request
Could you please clarify:

1. The recommended workflow for publishing nodes with multiple Python version builds
2. Whether the documentation can be updated to include this use case
3. Any best practices or examples from other custom nodes that handle this scenario

Thank you for your time and assistance!