Skip to content

v0.6.2

Choose a tag to compare

@github-actions github-actions released this 16 Nov 16:45
· 69 commits to master since this release
5d9131d

Changed

  • Checks and releases run in one place: GitHub. .github/workflows/ci.yml runs
    on every push and pull request (gofmt, go mod tidy -diff, go vet,
    go build, cross-build for darwin/arm64, darwin/amd64 and linux/arm64,
    tests with -race, golangci-lint from .golangci.yml, govulncheck,
    gitleaks over the whole history, docs-check, node --check and a
    docker build of both image targets), codeql.yml scans Go and the panel's
    JavaScript, dependency-review.yml fails a pull request that adds a
    dependency with a high-severity advisory, and Dependabot proposes updates
    weekly. Gitea keeps the code mirror and one workflow, images, which builds
    slim/full on a tag and pushes them to the host registry — GitHub cannot
    log in there (403). Its ci.yml and release.yml are gone, so tests and
    release archives are built once, on GitHub, and the release publishes them
    together with the GHCR images.
  • The pipeline is hardened: actions are pinned to commit SHAs, permissions
    default to contents: read, checkout leaves no token behind
    (persist-credentials: false), pull requests receive no repository secrets,
    and the scanners install their own tools instead of pulling third-party
    actions.

Docs

  • docs/en/dev/release.md and docs/ru/dev/release.md describe the single
    builder, the list of checks and what keeps the pipeline itself safe;
    docs/en|ru/dev/development.md points at the same file instead of repeating
    the job list.