No rule to define package deprecation or end of life #141

New Issue

GiteaMirror · 2026-02-17T11:22:33-06:00

GiteaMirror commented

2026-02-17 11:22:33 -06:00

Originally created by @hparra on GitHub (Jul 18, 2014).

There is no rule to mark an entire package as deprecated or end of life (EOL).

Such a semver would be useful to communicate one or more or the following:

the package has been superseded by another package
the package is no longer developed or maintained
the package parent software or system is obsolete

Proposed grammar:

<valid semver> ::= <version core>
                 | <version core> "-EOL"
                 ... etc.

Not sure if -final is more or less appropriate. I don't have a strong opinion regarding casing.

I'm willing to propose or collaborate on language to produce PR.

Originally created by @hparra on GitHub (Jul 18, 2014). There is no rule to mark an entire package as deprecated or end of life (EOL). Such a semver would be useful to communicate one or more or the following: - the package has been superseded by another package - the package is no longer developed or maintained - the package parent software or system is obsolete Proposed grammar: ``` <valid semver> ::= <version core> | <version core> "-EOL" ... etc. ``` Not sure if `-final` is more or less appropriate. I don't have a strong opinion regarding casing. I'm willing to propose or collaborate on language to produce PR.

GiteaMirror closed this issue

2026-02-17 11:22:34 -06:00

GiteaMirror commented

2026-02-17 11:22:35 -06:00

@FichteFoll commented on GitHub (Jul 18, 2014):

I do not think this should be part of the version number and rather be handled by the respective package manager.

@FichteFoll commented on GitHub (Jul 18, 2014): I do not think this should be part of the version number and rather be handled by the respective package manager.

GiteaMirror commented

2026-02-17 11:22:35 -06:00

@tomByrer commented on GitHub (Sep 19, 2014):

In 2 of the 3 scenarios above, it is unlikely there will be a response to outside PRs. Like Fichte said, the PM could add a note in the metadata: 2.9.0+eol. Perhaps that use-case for metadata can be mentioned in the doc?

@tomByrer commented on GitHub (Sep 19, 2014): In 2 of the 3 scenarios above, it is unlikely there will be a response to outside PRs. Like Fichte said, the PM could add a note in the metadata: `2.9.0+eol`. Perhaps that use-case for metadata can be mentioned in the doc?

GiteaMirror commented

2026-02-17 11:22:36 -06:00

@jwdonahue commented on GitHub (Dec 6, 2017):

Perhaps an EOL tag, could be added that begins with something other than the prerelease tag mark? My view is that build meta should be renamed user data and any semantics, ordering or internal syntax should be left up to the implementer. Putting EOL in the prerelease tag would be useless because it would have lower precedence than whatever the last non-prerelease version was.

@hparra, if you are not planning on issuing a PR with proposed changes, please close this issue at your earliest possible convenience. It seems unlikely that any new fields would be accepted into the standard. Perhaps if the maintainers ever decide to open a 3.x.x branch this issue could be revived then?

@jwdonahue commented on GitHub (Dec 6, 2017): Perhaps an EOL tag, could be added that begins with something other than the prerelease tag mark? My view is that build meta should be renamed user data and any semantics, ordering or internal syntax should be left up to the implementer. Putting EOL in the prerelease tag would be useless because it would have lower precedence than whatever the last non-prerelease version was. @hparra, if you are not planning on issuing a PR with proposed changes, please close this issue at your earliest possible convenience. It seems unlikely that any new fields would be accepted into the standard. Perhaps if the maintainers ever decide to open a 3.x.x branch this issue could be revived then?

GiteaMirror commented

2026-02-17 11:22:37 -06:00

@jwdonahue commented on GitHub (Oct 8, 2018):

@hparra, can you please close this issue? It's not getting any traction.

@jwdonahue commented on GitHub (Oct 8, 2018): @hparra, can you please close this issue? It's not getting any traction.

GiteaMirror commented

2026-02-17 11:22:38 -06:00

@steveklabnik commented on GitHub (Feb 11, 2019):

I do not think this should be part of the version number and rather be handled by the respective package manager.

This is the answer. Semver versions and releases are immutable, so mutating the version string doesn't work. This kind of thing is outside of the purview of semver, and is a job for the particular package manager.

Thanks!

@steveklabnik commented on GitHub (Feb 11, 2019): > I do not think this should be part of the version number and rather be handled by the respective package manager. This is the answer. Semver versions and releases are immutable, so mutating the version string doesn't work. This kind of thing is outside of the purview of semver, and is a job for the particular package manager. Thanks!

GiteaMirror referenced this issue

2026-04-16 10:01:18 -05:00

[GH-ISSUE #141] Is the PATCH needed? #956

GiteaMirror referenced this issue

2026-04-20 09:26:57 -05:00

[GH-ISSUE #141] Is the PATCH needed? #1823

GiteaMirror referenced this issue

2026-04-25 16:44:04 -05:00

[GH-ISSUE #141] Is the PATCH needed? #2805

GiteaMirror referenced this issue

2026-06-13 12:04:51 -05:00

[GH-ISSUE #141] Is the PATCH needed? #4334