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

[GH-ISSUE #367] Deprecation and how to do it #1140

New Issue
Closed
opened 2026-04-16 10:24:19 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-16 10:24:19 -05:00
Owner
Copy Link

Originally created by @dret on GitHub (Apr 28, 2017).
Original GitHub issue: https://github.com/semver/semver/issues/367

reading that deprecation should be announced via a minor version before being rolled out: would https://tools.ietf.org/html/draft-wilde-sunset-header help as a way to do it? after all, the deprecation notice ideally should be machine-understandable and ideally, this shouldn't have to be re-invented by every single API individually.

Originally created by @dret on GitHub (Apr 28, 2017). Original GitHub issue: https://github.com/semver/semver/issues/367 reading that deprecation should be announced via a minor version before being rolled out: would https://tools.ietf.org/html/draft-wilde-sunset-header help as a way to do it? after all, the deprecation notice ideally should be machine-understandable and ideally, this shouldn't have to be re-invented by every single API individually.
GiteaMirror commented 2026-04-16 10:24:19 -05:00
Author
Owner
Copy Link

@dret commented on GitHub (Apr 28, 2017):

i just added d5b738d49e (deprecation) as one scenario to the draft. i am planning on publishing a new version soon.

<!-- gh-comment-id:297976345 --> @dret commented on GitHub (Apr 28, 2017): i just added https://github.com/dret/I-D/commit/d5b738d49e59b124dcee84cee8f3e435efecb293 (deprecation) as one scenario to the draft. i am planning on publishing a new version soon.
GiteaMirror commented 2026-04-16 10:24:20 -05:00
Author
Owner
Copy Link

@jwdonahue commented on GitHub (Nov 28, 2017):

It seems likely that for service interfaces over HTTP, https://tools.ietf.org/html/draft-wilde-sunset-header would be a wise choice, in conjunction with the specified SemVer behavior.

The Sunset HTTP Header is beyond the scope of the SemVer specification. Please close this issue at your earliest convenience.

<!-- gh-comment-id:347495210 --> @jwdonahue commented on GitHub (Nov 28, 2017): It seems likely that for service interfaces over HTTP, [https://tools.ietf.org/html/draft-wilde-sunset-header](https://tools.ietf.org/html/draft-wilde-sunset-header) would be a wise choice, in conjunction with the specified SemVer behavior. The Sunset HTTP Header is beyond the scope of the SemVer specification. Please close this issue at your earliest convenience.
GiteaMirror commented 2026-04-16 10:24:20 -05:00
Author
Owner
Copy Link

@dret commented on GitHub (Nov 28, 2017):

not a problem. thanks for looking into it.

<!-- gh-comment-id:347497022 --> @dret commented on GitHub (Nov 28, 2017): not a problem. thanks for looking into it.
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#1140
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?