* Change the go module path
from github.com/csaf-poc/csaf_distribution to github.com/gocsaf/csaf.
* Rename archive for release tarballs.
* Adjust testing scripts and documentation.
* make jsonschema loading work with current versions of the jsonschema library
again and simplify the code while at it.
* Improve itest workflow for validation service, to make them more robust.
* Use a github action to setup nodejs and use a version that is
required by https://github.com/secvisogram/csaf-validator-service/.
* Add nodejs16 installation to prepareUbuntuInstanceForITests.sh.
(so it can be done once in manual settings)
* Add refreshing of apt cache before apt install because sometimes
the cached ubuntu image does not have the apt cache current.
---------
Co-authored-by: Bernhard Reiter <bernhard@intevation.de>
* Add short description for each component in the main README
* Move more Info in separated files.
* Add hint that csaf_provider offers a service interface.
* Explain why windows only has uploader and checker.
Co-authored-by: Bernhard Reiter <bernhard@intevation.de>
* Add only uploader and checker binaries and basic documentation to windows dist archive.
Prepare for specific docs.
* Improve Makefile to be able to use github lightweight git tags for release version calculation.
* Change github action to use the make dist target for asset uploading.
* Remove matrix strategy and single go release actions.
* Update go setup action to use latest version.
* Use action to upload both distribution archives created by make.
* Improve the pattern to leave tagged release version numbers like
`0.2.2-alpha` alone and only increase version numbers where
git describe has added a string starting with a number.
* Add flag to display the version for each binary. It is based on `git describe` but adds
a number to the PATCH level if we are between annotated tags, so makes it semver.org
compatible. Use the "-ldflags" method that also works with go 1.17.
* Use Makefile bash and sed magic to do PATCH level increase if needed.
Co-authored-by: Bernhard Reiter <bernhard@intevation.de>
* Change mechanics to use a variable to indicate if a tag build is
wanted. Add ability to specify tag explictely.
* Use variables to have only one build recipe.
* Place binaries in target specific bin- directories.
* Do not return to main branch as it may not be the original branch we
were on. Turn this into a warning.
* "build_linux": building for GNU/linux
* "build": Building for both linux and windows (cross build)
* Place the generate binaries under "binaries/" directory
* Improve echo messages
* Makefile with the following targets
** build for (linux system)
** build_win (windows system)
** build_tag (build from the last tag)
** clean for (removing the binaries)
* Adjust README file
