This replaces the docker image so that we get one that has all of these
commands available: make, git, go, python2 and perl.
We can now run `make generate` in the steps used to generate the release patch,
so the release patch contains the builtin_metadata.json changes.
Before, we had been running `make generate` in the working directory, and
copied the file into the container's workdir; but that left the working
directory modified, and hindered patch application before cleaning up.
Signed-off-by: Stephan Renatus <stephan.renatus@gmail.com>
This commit improves the release-patch target to mention users in the
Miscellaneous section and warn if a GitHub token is not provided.
Signed-off-by: Torin Sandall <torinsandall@gmail.com>
Bugfixes are done on branches that don't have an unreleased
section in the CHANGELOG which would cause the last line
to be deleted and the change put at the bottom of the
CHANGELOG. Now there is a test for the unreleased section
which if it exists does the old behavior. If not the new
message will be placed above the last version section.
Fixes: #2533
Signed-off-by: Joshua Shanks <jjshanks@gmail.com>
Co-authored-by: Stephan Renatus <stephan.renatus@gmail.com>
The decision logger unit tests had to be updated to always set the
version.Version value because they are sensitive to changes in the
payload sizes.
Signed-off-by: Torin Sandall <torinsandall@gmail.com>
We were using a file with hard coded versions to display docs for, but
this complicates things if/when we need to do patch releases on
different branches from master.
Signed-off-by: Patrick East <east.patrick@gmail.com>
The process is pretty easy, just add a new line in RELEASES with the
version number. Once that git tag is available it will start to show
up on subsequent builds.
Signed-off-by: Patrick East <east.patrick@gmail.com>
Previously the release script always computed LAST_VERSION from tags. We
recently published 0.9.3-rc tags for test purposes. This was preventing
thes cript generating the patch for the markdown/yaml files in the docs
that refer to the OPA version. These changes allow the caller to control
the LAST_VERSION so the docs get updated accordingly.
Signed-off-by: Torin Sandall <torinsandall@gmail.com>
These changes contain a redesign of the OPA website. The main changes
are (1) new frontpage w/ refreshed messaging and assets and (2) docs
ported to gitbook.
- Add script to build release artifacts from inside a container. In the past,
release artifacts have been created from a clean checkout, but this should be
much more reliable.
- Add script to generate release patch from tip. In the past, the release
patch changes have been made manually.
Johan Fylling