LearningCircuit
64d326dda2
Create Release / security-gate (push) Failing after 0s
Create Release / build (push) Has been skipped
Create Release / provenance (push) Has been skipped
Create Release / create-release (push) Has been cancelled
Create Release / trigger-workflows (push) Has been cancelled
Separate RUN instructions in the builder stage are intentional for Docker layer caching — npm ci, npm run build, and pdm install have different change frequencies and merging them would force expensive re-downloads when only one step's inputs change.
25 lines
1016 B
YAML
25 lines
1016 B
YAML
# Hadolint configuration file
|
|
# See https://github.com/hadolint/hadolint#configure
|
|
|
|
# Ignore rules that are impractical for our use case
|
|
ignored:
|
|
# DL3008: Pin versions in apt-get install
|
|
# Rationale: Pinning apt package versions is impractical because:
|
|
# - Debian package versions change frequently between releases
|
|
# - We use digest-pinned base images for reproducibility
|
|
# - Pinned versions would require constant maintenance
|
|
- DL3008
|
|
|
|
# DL3013: Pin versions in pip
|
|
# Rationale: We install build tools (pdm, playwright) where we want
|
|
# the latest compatible version. The actual application dependencies
|
|
# are pinned in pdm.lock which provides reproducibility.
|
|
- DL3013
|
|
|
|
# DL3059: Multiple consecutive RUN instructions
|
|
# Rationale: Separate RUN instructions are intentional for Docker layer
|
|
# caching. npm ci, npm run build, and pdm install have different change
|
|
# frequencies — keeping them separate avoids expensive re-downloads when
|
|
# only one step's inputs change.
|
|
- DL3059
|