How do you version shared CI steps and handle breaking changes?
This tests CI hygiene and consumer safety. Pin shared steps to immutable tags or SHAs, use semantic versioning, and force consumers to opt into breaking changes. Red flag: referencing a mutable branch like main for reusable workflows.
This tests whether you protect downstream pipelines from surprise failures. A strong answer recommends immutable versioning: tag releases with semantic versions or commit SHAs, never a floating branch reference. Consumers pin to a specific tag so breaking changes cannot accidentally break their builds. When you ship a breaking change, you publish a new major version tag and let teams migrate on their own schedule. Red flag: suggesting all pipelines automatically track main, which destroys reproducibility and creates production incidents.
Read the original → docs.github.com
- #ci/cd
- #github actions
- #versioning
- #reusable workflows
- #devops
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.