Octopus specifications and related TypeScript type definitions.
The project is setup as a mono-repo (using Yarn Workspaces), contains following packages:
@opendesign/octopus-oas OpenAPI v3 Specification of the Octopus format@opendesign/octopus-ts TypeScript definitions auto generated from octopus-oas@opendesign/manifest-oas OpenAPI v3 Specification of the Octopus Manifest format@opendesign/manifest-ts TypeScript definitions auto generated from manifest-oasBoth the OAS projects contain openapi.yaml file as a specs definition entry-point, all of the actual schema definitions are in placed in schemas sub-directory.
Specification source is a structure of individual mutually referenced .yaml files, although the final result is always a single JSON file.
The specification development should be only a matter of updating the schema files. There's yarn build script at the top-level as well as in each workspace that creates the output and runs liters where needed.
To realease the specs the version needs to be bumped first. There's a convention that all the packages in the project share the same version. There are four scripts for update of a particular SemVer number:
yarn version:bump:major
yarn version:bump:minor
yarn version:bump:patch
yarn version:bump:alphaThis step bumps version in all the packages, commits the changes and tags that commit with a version label.
So far all the changes were done locally. One can check the git log to verify everything is as intended.
Note that this might change in the future and the whole process might get automated by joining the two publish steps
There are two options for the actual publish step. Manual or automated via Gitlab CI runner.
Although 'manual' is not the recommended way of how to publish the packages, it's here for convenience and overall process speed-up. However, caution is advised when using manual publish
It's expected the user is already logged into the publish registry.
Then the script is just
yarn releaseThe standard way of publishing the packages is to push the tag created by 'Version Bump' step into Gitlab and let the CI runner do the job.
git push --follow-tags