Brian C. Lane 58839cf927 Use semver to enforce blueprint version numbers ... This changes osbuild-composer's behavior to match lorax-composer when encountering invalid versions. Instead of leaving them as-is it will return a BlueprintError explaining the problem. eg. "errors": [ { "id": "BlueprintsError", "msg": "Invalid 'version', must use Semantic Versioning: is not in dotted-tri format" } ] This is enforced on new blueprints (including the workspace). If a previously stored blueprint has an invalid version and a new one is pushed it will use the new version number instead of trying to bump the invalid one. This also moves the version bump logic into blueprint instead of store, and adds an Initialize function that will make sure that the blueprint has sane default values for any missing fields. This includes tests for the Initialize and BumpVersion functions.		2020-02-25 09:00:35 +01:00
..
go-semver	Use semver to enforce blueprint version numbers	2020-02-25 09:00:35 +01:00
go-systemd	go: include vendored modules	2020-02-17 16:09:17 +01:00