Repository navigation
chore: organize legacy images under v1 - #264
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Move the existing images into
v1/so calendar-versioned generations can coexist at the repository root, preparing the layout for #231. Group Caddy, Nginx, dev and OpenTelemetry variants under their runtime family; published image tags and image contents remain unchanged.Update Bake contexts, build workflows, security scan paths, the PHP matrix updater and build documentation. Move shared scripts into
scripts/, rename the build workflows to identify v1, and remove the Docker Hub README sync, Dockerfile lint and ShellCheck workflows.Validation:
actionlint, Node syntax check andgit diff --checkpass.Full image builds were not run.