v0.6.6
registry
tool improvements + linter plugins
This release includes a change to the registry
tool that allows registry apply
to automatically zip directories of spec files when it uploads them. This allows these files to be stored in git repositories or other staging areas in human readable forms (no more zip archives in git repos). If the mime type in info.yaml
includes +zip
, then registry apply
first looks for a zip archive, and if none is found, all of the other files alongside the info.yaml
are zipped and uploaded as the spec contents.
Release builds now also include linter plugins, which make it easier to run registry compute conformance
-- external linters (typically Spectral and Google's API Linter) still require separate installation, but the plugins that the registry
tool uses to call them are now stored alongside the registry
tool.
Changelog
- 2db14e7 fix archives to use default build (#1061)
- 8cc6332 remove build of registry-server (#1060)
- 1c3571b fix build (#1059)
- 5c184e4 Regenerate generated code to pick up random format changes. (#1058)
- 5090afc Support for field definition and storage. (#1046)
- 19e3c2d add registry-server and linter plugins to release (#1057)
- a2537fe Automatically create zip archives when needed by
registry apply
. (#1055) - 6ac8d71 verify that version state is a represented lifecycle stage (#1051)
- 2e467a0 add repo token to avoid rate limit build failures (#1052)
- 3b2d007 Run ./tools/pretty.sh to format README.md files. (#1050)
- 72a9ca5 Add a script that installs the latest release of the registry tool. (#1049)