Releases: atc0005/go-ci
Releases · atc0005/go-ci
Release v0.2.1
Changed
- Update golangci/golangci-lint from
v1.29.0
tov1.30.0
- binary installed within
oldstable
,stable
andunstable
images - Docker image used as a builder/base for
lint-only
image
- binary installed within
References
- See the
v0.2.1
milestone for the issues associated with this release. - See our CHANGELOG for more information.
Release v0.2.0
Added
- Bundle
golangci-lint
andmarkdownlint
config files- provide a usable default baseline for our projects, hopefully for others
also
- provide a usable default baseline for our projects, hopefully for others
Fixed
- Fix Makefile recipe description
References
- See the
v0.2.0
milestone for the issues associated with this release. - See our CHANGELOG for more information.
Release v0.1.1
Changed
lint-only
image- swap base image from
golang
andalpine
togolangci/golangci-lint
- the intent is to provide a working environment for
golangci-lint
- the intent is to provide a working environment for
- swap base image from
Fixed
lint-only
imagegolangci-lint
requires working go environment
References
- See the
v0.1.1
milestone for the issues associated with this release. - See our CHANGELOG for more information.
Release v0.1.0
Added
-
Add Docker containers for linting, testing, building in place of
actions/setup-go
provided environment currently used by most of my Go
projects- "old stable"
- Go 1.13.x series (currently)
- "stable"
- Go 1.14.x series (currently)
- "linting-only"
- bundles
staticcheck
,golangci-lint
linting tools into a thin image
- bundles
- "unstable"
- Go 1.15rc1 (currently)
- "old stable"
-
Include common linting tools used by my Go projects
staticcheck
,golangci-lint
-
Add GitHub Actions workflows
- lint Markdown documentation
- lint Dockerfile files
-
Add Dependabot updates
- GitHub Actions
- Go modules
- using a "trick" to have a
tools
module that depends on the linting
tools that we include in our container images
- using a "trick" to have a
- Dockerfile base images
References
- See the
v0.1.0
milestone for the issues associated with this release. - See our CHANGELOG for more information.