-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Description
describe the feature you'd like to see
Context
I'm working on integrating Cobalt into automation tools and infrastructure scripts (specifically for ProxmoxVE Helper Scripts community project), but I've noticed that this repository doesn't have any GitHub Releases with version tags.
Feature Description
It would be extremely beneficial if Cobalt could implement a versioning system with tagged releases on GitHub. This would allow:
- Reproducible deployments: Users can pin to specific, stable versions rather than always pulling from
main - Change tracking: Clear changelog and version history
- Integration with package managers and automation tools: Many tools (like the ProxmoxVE community scripts) require tagged releases to ensure stability
- Semantic versioning: Clear understanding of breaking changes, features, and fixes
Use Case
Currently, the ProxmoxVE Helper Scripts project requires all applications to use tagged releases via their fetch_and_deploy_gh_release function. They explicitly prohibit git clone from main branches because:
- If upstream breaks something on main, users report issues to them
- No guarantee of stability or reproducibility
- Cannot track what version users are running
Without tagged releases, Cobalt cannot be added to their repository, which limits its reach to the Proxmox community.
Proposed Implementation
- Adopt semantic versioning (e.g., v1.0.0, v1.1.0, etc.)
- Create GitHub Releases with tags for major milestones
- Include release notes with each version
- Optionally: Attach compiled assets or source archives to releases
This would make Cobalt more accessible to automation tools, package managers, and enterprise users who need version stability.
Thank you for considering this feature!
additional context
No response