Closed vdice closed 4 years ago
@technosophos I just realized the following: I had centered CI around git tags but I now recall that we have a precedent of pushing spec versions to separate branches. Can we change the process to instead cut tags for each future spec version? Or should I adjust this process to trigger on branch creation? (May be trickier to ignore potential non-version-related branches, etc.)
@technosophos I just realized the following: I had centered CI around git tags but...
Discussion transitioned to https://github.com/cnabio/cnab-spec/issues/351
I think we can publish a tag for 1.0.1 if we need to get this working.
I think we can publish a tag for 1.0.1 if we need to get this working.
It looks like a tag can't be pushed with the same name of a branch. I've manually uploaded the schema artifacts from the cnab-core-1.0.1
branch as a stop-gap 👍 .
Contributes towards https://github.com/cnabio/cnab-spec/issues/346 Depends on https://github.com/cnabio/cnab.io/pull/32 (merged)
TODO (after approval):
validation
tocnab-spec-validate
: