Commits to master run the updatePreReleaseVersion.js which changes the version number to the output of git describe --tags which is LATEST_TAG-NUM_COMMITS_SINCE_TAG-HASH, eg: v0.3.0-1-HHHHHH or if a beta(next bullet) has been publisehd v0.4.0-beta-1-HHHHHH. It is then published to the next tag on npm This allows for testing the latest version of master via the next tag on npm.
Tags containing beta are published to the next tag on NPM. This will allow testing of things that check against version number changes.
latesttagupdatePreReleaseVersion.jswhich changes the version number to the output ofgit describe --tagswhich isLATEST_TAG-NUM_COMMITS_SINCE_TAG-HASH, eg:v0.3.0-1-HHHHHHor if a beta(next bullet) has been publisehdv0.4.0-beta-1-HHHHHH. It is then published to thenexttag on npm This allows for testing the latest version of master via thenexttag on npm.betaare published to thenexttag on NPM. This will allow testing of things that check against version number changes.I tested this via the platform plugin since it is a private project for now, and it works as expected. https://www.npmjs.com/package/@serverless/platform-plugin https://travis-ci.com/serverless/platform-plugin/branches (beta is latest not next because i published that before devising this scheme)
Combined with https://github.com/serverless/platform-plugin/pull/12 will make using dev platform as simple as: