4 Commits
Author SHA1 Message Date
Djeex 5a7a60d299 CI/CD hardening: lint, secret scan, coverage gate, auto CVE-fix PRs, GHCR + GitHub mirror publishing (#32)
CI / build-and-scan (push) Successful in 1m37s
- release changelog: commits rendered as description (link), divider lines dropped
- gitleaks secret scan and hadolint on every push/PR
- ruff lint/format gate (Python repos) with a pytest --cov-fail-under gate
- scheduled CRITICAL Trivy failures attempt an apk upgrade rebuild and open a follow-up PR if it clears the finding, instead of just failing red
- images also published to ghcr.io/djeex/<repo>
- a matching GitHub Release is created on the GitHub mirror, with a notice pointing back to this repo as the source of truth
2026-08-26 15:43:40 +02:00
Djeex b0a220e7a2 Link each commit in the release changelog to its own commit page
CI / build-and-scan (pull_request) Successful in 56s
COMMIT_LIST only rendered the bare subject line per commit, with no
way to jump to that specific commit — only the triggering commit
(Source:) had a link. Each line now reads
"- [<short-sha>](<repo>/commit/<sha>) <subject>", matching the same
link style already used for Source.
2026-08-23 23:20:51 +02:00
Djeex ae737c0bd0 Align CI release workflow with adguard-cidre/socat-proxy template
CI / build-and-scan (pull_request) Successful in 1m59s
The publish/release step had drifted from the sibling repos' reference
template: PR-number extraction relied on the local commit log after
the version-bump commit was already made, so it could never find the
triggering PR (that commit's own message has no PR reference) — fixed
by keying off github.sha, the fixed triggering commit, instead.

Also aligned: docker login casing (Djeex, not djeex), Trivy pinned to
0.74.0, deprecation check made informative instead of build-blocking,
publish skipped entirely when no container-relevant file changed, and
the release body now lists the individual commits (with a --- divider
under each heading) instead of the raw changed-files list.
2026-08-23 22:39:58 +02:00
Djeex 530aeba667 Add Gitea Actions CI/CD pipeline
Bring nvidia-stock-bot up to the same CI/CD maturity as adguard-cidre:
pytest suite (19 tests), multi-stage Dockerfile with a dedicated test
stage, pinned requests dependency, Gitea Actions workflow (build, smoke
test, unit tests, deprecation check, Trivy critical/high scan, version
bump + registry publish + release), and a Renovate config for automated
dependency updates.
2026-08-22 22:54:18 +02:00