github-starred/semver
2
0
Fork 0
mirror of https://github.com/semver/semver.git synced 2026-07-10 19:50:47 -05:00
Code Issues 1.0k Packages Projects Releases 4 Wiki Activity

[GH-ISSUE #852] Should you use alpha/beta in a 0.y.z version? #4796

New Issue
Closed
opened 2026-06-13 13:11:58 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-06-13 13:11:58 -05:00
Owner
Copy Link

Originally created by @katistix on GitHub (Jul 8, 2022).
Original GitHub issue: https://github.com/semver/semver/issues/852

I have a project currently on 0.2.2. After adding some features it will increment to 0.3.0, but the current available version is not complete. (To be more precise, it's an API where you can upload and delete files on a server) but right now you can only upload. I see the upload/remove as a SINGLE feature.

Can I release the current version under 0.3.0-alpha.1 to signal the fact that it is feature incomplete? Or is the alpha just for versions 1.0.0 and above?

Originally created by @katistix on GitHub (Jul 8, 2022). Original GitHub issue: https://github.com/semver/semver/issues/852 I have a project currently on 0.2.2. After adding some features it will increment to 0.3.0, but the current available version is not complete. (To be more precise, it's an API where you can upload and delete files on a server) but right now you can only upload. I see the upload/remove as a SINGLE feature. Can I release the current version under 0.3.0-alpha.1 to signal the fact that it is feature incomplete? Or is the alpha just for versions 1.0.0 and above?
GiteaMirror commented 2026-06-13 13:11:58 -05:00
Author
Owner
Copy Link

@ljharb commented on GitHub (Jul 8, 2022):

Yes, you can.

<!-- gh-comment-id:1178630089 --> @ljharb commented on GitHub (Jul 8, 2022): Yes, you can.
GiteaMirror commented 2026-06-13 13:11:59 -05:00
Author
Owner
Copy Link

@katistix commented on GitHub (Jul 8, 2022):

Thanks

<!-- gh-comment-id:1178630302 --> @katistix commented on GitHub (Jul 8, 2022): Thanks
GiteaMirror commented 2026-06-13 13:11:59 -05:00
Author
Owner
Copy Link

@Nixinova commented on GitHub (Jul 8, 2022):

You can do whatever you want with pre-release tags. Pre/post-1.0 doesn't mean anything in this case.

<!-- gh-comment-id:1178660219 --> @Nixinova commented on GitHub (Jul 8, 2022): You can do whatever you want with pre-release tags. Pre/post-1.0 doesn't mean anything in this case.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
consensus seeking
duplicate
extend
layout
pull-request
Mirrored from GitHub Pull Request
 question
RFC
spelling/grammar
staled
update
waiting for PR
won't fix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/semver#4796
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?