github-starred/conventionalcommits.org
2
0
Fork 0
mirror of https://github.com/conventional-commits/conventionalcommits.org.git synced 2026-03-22 12:44:37 -05:00
Code Issues 153 Packages Projects Releases Wiki Activity

Find a strategy to bump up the version #46

New Issue
Closed
opened 2026-02-17 11:38:32 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-02-17 11:38:32 -06:00
Owner
Copy Link

Originally created by @damianopetrungaro on GitHub (Aug 26, 2018).

@conventional-commits/committee we need to find a strategy to implement a proper semantic versioning when we'll release the first version (and it's pretty close).

What I propose is to use an upcoming directory where we change the latest specs version and when we decide to release (thanks to the conventional commits) we'll bump up the version and release.

Any other strategy is the welcome 😄

Originally created by @damianopetrungaro on GitHub (Aug 26, 2018). @conventional-commits/committee we need to find a strategy to implement a proper semantic versioning when we'll release the first version (and it's pretty close). What I propose is to use an `upcoming` directory where we change the latest specs version and when we decide to release (thanks to the conventional commits) we'll bump up the version and release. Any other strategy is the welcome 😄
GiteaMirror added the supporthelp wanted labels 2026-02-17 11:38:32 -06:00
GiteaMirror commented 2026-02-17 11:38:34 -06:00
Author
Owner
Copy Link

@damianopetrungaro commented on GitHub (Sep 16, 2018):

Automatically added to the new website structure!

@damianopetrungaro commented on GitHub (Sep 16, 2018): Automatically added to the new website structure!
GiteaMirror commented 2026-02-17 11:38:35 -06:00
Author
Owner
Copy Link

@bcoe commented on GitHub (Mar 12, 2019):

@damianopetrungaro 🎉

@bcoe commented on GitHub (Mar 12, 2019): @damianopetrungaro 🎉
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
discussion
enhancement
greenkeeper
help wanted
meeting-agenda
operations
process
pull-request
Mirrored from GitHub Pull Request
 question
suggestion
support
triaged
No Label help wanted support
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/conventionalcommits.org#46
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?