Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Feature/add preid param for semver

See original GitHub issue

Issue to discuss #83

The idea is to allow adding identifiers to certain tags upon release such as beta, dev, rc, etc.

The proposed command would be:

standard-version -p --tag="<identifier>"

So that running standard-version -p --tag="special-release" would result in a tag something like 2.0.0-special-release.0. Using the prelease command -p repeatedly on the same semver version results in an increment to the last number in the series. So running that previous command again would result in 2.0.0-special-release.1

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Reactions:1
  • Comments:8 (7 by maintainers)

github_iconTop GitHub Comments

bcoecommented, Nov 13, 2016

Hello all, sorry for being AWOL; npm, IstanbulJS, and yargs have all been quite busy lately and I’ve been spread a bit too thin.

Regarding incrementing logic:

I like this approach a lot as a start @AntJanus:

So running that previous command again would result in 2.0.0-special-release.1

Regarding named major releases:

Regarding named major releases, I’m inclined to keep that discussion out of this thread; not that it’s not a feature we should consider, but mainly it feels like a different set of concerns.


One standing question I have, is what does the changelog look like for pre-release versions, my preference would be having an Upcoming section in the; that would then become the next release, once a non-pre-release version is released. How do folks feel about this? I wonder how hard this would be to pull off.

bcoecommented, Dec 18, 2016

@Tapppi @AntJanus I agree, I’ve been using the new --prerelease and --release-as functionality, and I believe it does a good job of hitting an 80/20 with regards to cutting special releases.

Let’s move any further discussion about pre-release improvements to #146.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Semantic Versioning 2.0.0 | Semantic Versioning
Given a version number MAJOR.MINOR.PATCH, increment the: MAJOR version when you make incompatible API changes; MINOR version when you add functionality in a ......
Read more >
semver - npm Docs
Identifier to be used to prefix premajor, preminor,. prepatch or prerelease version increments. -l --loose. Interpret versions and ranges ...
Read more >
Security update for SUSE Manager Client Tools | SUSE Support
An update that fixes 13 vulnerabilities, contains 5 features is now available. Description: This update fixes the following issues:
Read more >
Change log for 4.8.23
#247 · Bug 1974718: Fix conditional order for setting net device param. ... Bug 1967208: Use semver to parse version for “Getting started”...
Read more >
2021-01-11. Fix issue #5409. 2021-01-11. Feature/add preid param for semver. 2021-01-11. MacOS - AesGcm Cryptography - No usable version of libssl was found....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found