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

[GH-ISSUE #25] FAQ typo: bugfix is patch-, not minor-level #885

New Issue
Closed
opened 2026-04-16 09:53:58 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-16 09:53:58 -05:00
Owner
Copy Link

Originally created by @patcon on GitHub (May 17, 2012).
Original GitHub issue: https://github.com/semver/semver/issues/25

What should I do if I update my own dependencies without changing the public API?

[...] Determining whether the change is a patch level or minor level modification depends on whether you updated your dependencies in order to fix a bug or introduce new functionality. I would usually expect additional code for the latter instance, in which case it's obviously a minor level increment.

If you'd expect additional code for the latter (new functionality), isn't the former bug fix option a patch level, not a minor level, increment?

Originally created by @patcon on GitHub (May 17, 2012). Original GitHub issue: https://github.com/semver/semver/issues/25 > ### What should I do if I update my own dependencies without changing the public API? > > [...] Determining whether the change is a patch level or minor level modification depends on whether you updated your dependencies in order to **fix a bug or introduce new functionality**. I would usually expect additional code for the **latter** instance, in which case it's obviously a **minor level** increment. If you'd expect additional code for the latter (new functionality), isn't the former bug fix option a **patch level**, not a minor level, increment?
GiteaMirror commented 2026-04-16 09:53:59 -05:00
Author
Owner
Copy Link

@ayust commented on GitHub (Jun 7, 2012):

Yes, and that's what the document as written implies. The latter (new functionality) is a minor level increment. Nothing in your quote states that a bugfix is minor level.

<!-- gh-comment-id:6185861 --> @ayust commented on GitHub (Jun 7, 2012): Yes, and that's what the document as written implies. The _latter_ (new functionality) is a minor level increment. Nothing in your quote states that a bugfix is minor level.
GiteaMirror commented 2026-04-16 09:53:59 -05:00
Author
Owner
Copy Link

@patcon commented on GitHub (Jun 7, 2012):

Oh good lord. I'm trying to understand how I was comprehending that before, and I can't really see it now. Oy. I think my brain was thinking that speaking in former-latter terminology means a juxtaposition is being formed. Sorry.

Might suggest this for dolts like me:

I would usually expect additional code for the latter instance, in which case that's obviously a minor level increment.

<!-- gh-comment-id:6186993 --> @patcon commented on GitHub (Jun 7, 2012): Oh good lord. I'm trying to understand how I was comprehending that before, and I can't really see it now. Oy. I think my brain was thinking that speaking in former-latter terminology means a juxtaposition is being formed. Sorry. Might suggest this for dolts like me: > I would usually expect additional code for the latter instance, in which case **that's** obviously a minor level increment.
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#885
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?