macro187 / verbot Goto Github PK

Store current version in NPM package.json.

i.e. master branches that branch from other master branches, not directly from the release subgraph.

Work from release-visible branch points out toward existing release-visible master branches, looking for feature/breaking commits.

[] How to find release-visible branch point for existing release-invisible branches?

[] Failure mode: Multiple branch points for the same future major release, e.g. breaking commits on two master branches within the same major series.

Show command(s) to undo a release once it's been done

calc
Guess based on branch

calc --release
Most recent release tag
+semver tags since then

calc --pre-release
Most recent release tag
Number of commits since then
+semver tags since then
Branch
Hash
1.0.0-alpha.+.

Push all necessary branches and tags according to check-remote

[x] Remote tags exist and are the same or don't exist
[x] Remote branches are same or behind local ones

After performing a release, show command(s) to push affected branches and tags

: [localmissing|remotemissing|localahead|remoteahead|conflicting]
: [localmissing|remotemissing|conflicting]

There is at least one location to record the current version.

All recorded versions are the same.

Warn about locations where version could be recorded but isn't.

Run it as a prerequisite to other commands where applicable.

--tight means == locked commit

--loose means >= locked commit within same major version

Maybe --loose is the default for day-to-day development, and --tight is opt-in for build servers etc.

Currently version numbers are persisted in <version> elements in .csprojs. Factor this behaviour out so support for additional mechanisms can be built.