Skip to content

Files

Latest commit

 

History

History

docker

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
Dockerfile.bun
Dockerfile.bun
 
 
Dockerfile.bundler
Dockerfile.bundler
 
 
Dockerfile.cargo
Dockerfile.cargo
 
 
Dockerfile.composer
Dockerfile.composer
 
 
Dockerfile.devcontainers
Dockerfile.devcontainers
 
 
Dockerfile.docker
Dockerfile.docker
 
 
Dockerfile.docker-compose
Dockerfile.docker-compose
 
 
Dockerfile.dotnet-sdk
Dockerfile.dotnet-sdk
 
 
Dockerfile.elm
Dockerfile.elm
 
 
Dockerfile.github-actions
Dockerfile.github-actions
 
 
Dockerfile.gitsubmodule
Dockerfile.gitsubmodule
 
 
Dockerfile.gomod
Dockerfile.gomod
 
 
Dockerfile.gradle
Dockerfile.gradle
 
 
Dockerfile.maven
Dockerfile.maven
 
 
Dockerfile.mix
Dockerfile.mix
 
 
Dockerfile.npm
Dockerfile.npm
 
 
Dockerfile.nuget
Dockerfile.nuget
 
 
Dockerfile.pip
Dockerfile.pip
 
 
Dockerfile.proxy
Dockerfile.proxy
 
 
Dockerfile.pub
Dockerfile.pub
 
 
Dockerfile.swift
Dockerfile.swift
 
 
Dockerfile.terraform
Dockerfile.terraform
 
 
Dockerfile.uv
Dockerfile.uv
 
 
README.md
README.md
 
 
containers.json
containers.json
 
 

README.md

Dependabot Containers

This Action uses two Dependabot containers from the GitHub Container Registry to perform jobs.

In order to ensure that any given release of the Action deterministically uses the same, tested containers we use these Dockerfiles to check-in the specific SHA for each.

This allows us to use Dependabot to keep these SHAs up to date as new versions of the container are published.

These Dockerfiles are not actually built by the Action or any CI processes, they are purely used as compile-time configuration to generate containers.json which is used at runtime.