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.

Add build-metadata to lerna version / publish

See original GitHub issue

The semver standard provides for a ‘build-metadata’ section in the version number, which is separated from the pre-release identifers by a plus-sign (+).

The examples given are +001, +20130313144700, +exp.sha.5114f85.

I would like to see an argument to lerna version and publish that would apply this build metadata consistently across all packages in the repo (irrespective of independent vs fixed versioning)

This is not currently workaroundable with something like --preid=foo+bar, because:

This would create a version number like 1.0.0-foo+bar.0, rather than 1.0.0-foo.0+bar
build-metadata is valid to append to release versions (not just pre-releases)

Issue Analytics

State:
Created 3 years ago
Reactions:6
Comments:9

Top GitHub Comments

1reaction

JamesHenrycommented, Dec 13, 2022

So sorry for the delay on this one folks, let’s get @rrhodes PR over the line!

1reaction

rrhodescommented, Jun 27, 2021

@rrhodes hey good work on the PR!

Can you help to publish it temporarily (with fork disclaimer perhaps) so that I could have a way to test it as well?

Hello @josteph, if you would like to test my changes for Lerna, you should be able to run this from your machine if you pull down my branch of work.

Hoping to have these changes reviewed soon - waiting to hear from Lerna maintainers.

Top Results From Across the Web

Version and Publish - Lerna

Lerna can increment your package's versions as well as publish your packages to NPM, and it provides a variety of options to make...

Publish and download universal packages with Azure Artifacts

How to publish and download universal packages to and from ... Package versions must be lowercase without build metadata (+ suffix).

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 ......

Automatic versioning in a Lerna monorepo using Github actions

Integrate Lerna in a CI flow to automatically version and publish ... Next, we will add a job to the workflow and configure...

Version Incrementing - GitVersion

It is important to note that build metadata is not part of the semantic ... Adding +semver: breaking or +semver: major will cause...