folio-testing.aws.indexdata.com does not use latest stripes-connect etc.

Closing issue. Opened related issue to investigate other solutions for CI package versioning.

John, why don't you close this one – since the actual bug is fixed – and add a new one for the nicer generated-package version numbers?

Super-high patchlevels is an interesting idea. I like it. Let me chew on that.

Thanks, John, got it. The key bit I was missing i that you are now overwriting your previous build/install of the package each time.

0.16.1-SNAPSHOT.23 > 0.15.0 is NOT true

That is so broken it hurts. Is it special to "SNAPSHOT"? Could we use some other term?

Or just use super-high patchlevels, like 0.16.10003

Every time there is a commit to master, a build is triggered in Jenkins which, for Stripes and UI modules, essentially does an 'npm install' and 'npm publish'. The 'publish' is performed to a CI NPM repository. The package versions that are published are the same versions specified in the package.json and the existing package in the CI NPM repository from the previous CI build is overwritten with the latest one. That is why the package version is the same as the 'released' version but the contents are HEAD of master.

This is less than ideal of course, because you'd like more accurate information about which version of an NPM package you are using which is the problem I attempted to solve in , however, because of the lame way NPM handles "prerelease" dependency resolution, the solution implemented in caused problems with some of the core stripes packages which is why I've had to reverse some of the changes I made to how those core stripes dependencies are packaged for snapshot testing.

Let me know if this still doesn't make sense. I'd like to solve this problem for all NPM snapshot packages but, at the same time, I don't want to break everything while trying to figure out a better solution.