Releases: Financial-Times/golang-ci-orb
v2.0.0
v1.3.9
Merge pull request #43 from Financial-Times/fix/golancli-lint-version…
v1.3.8
Removed GO111MODULE and updated Lint version
Removed GO111MODULE env var and Updated Lint version (#41) * Update versions of golangci-lint and go itself. * Removed GO111MODULE env var * fixup! Update versions of golangci-lint and go itself. * fixup! fixup! Update versions of golangci-lint and go itself. * fixup! fixup! fixup! Update versions of golangci-lint and go itself. --------- Co-authored-by: Todor Videv <[email protected]>
Upgrade Snyk scanning go image
What's Changed
- Upgrade Snyk scanning go image by @asparuhft in #39
- Upgrade Snyk scanning go image by @asparuhft in #40
Full Changelog: v1.3.4...v1.3.6
Contributors
Assets 2
Set manually the env vars from env_var_name parameters
The parameters of type env_var_name are holding the name of environment variable, not its value.
Most probably due to the specific handling of parameters of type env_var_name, there is a complication in passing their values to a script. Their values are not passed to a script environment as are passed parameters of other types.
So we are setting them manually in the environment.
Fix scan job referring to wrong script.
Make the orb pack step required before deploy to prod step.
Use semantic versioning standard for orb deploy tags
Previous versions of the orb publishing workflow used orb specific naming convention for the tags that can trigger deploy to the CircleCI registry. The current standard that CircleCI uses is semantic versioning.
Move linters config file to the orb repo, remove deprecated linters.
If the param golang-config has value different than empty string, the orb lint step will keep its previous behaviour. The linters config will be obtained from this param.
The golang-config should specify url from which the config can be downloaded via wget.
However, now by default the golangci-config param is empty string and the linters config file will be copied from the orb repo to the CricleCI job executor’s filesystem.
Update CI/CD of the orb to latest orb-tools
Update the orb-tools to version the latest one.
Use dynamic configs for triggering the integration tests and deploy to production.
Use the recommended steps for the CI/CD of the orb and the recommended structure of the orb repo according to the official orb template.