| name | release-and-rollout |
| description | How a change in this repo actually reaches CI - the two tag series, cutting a v* source tag, publishing an orb version, and bumping consumer pins. Read this before or after merging any fix that needs to run in production CI. |
Release and rollout
Merging a PR here deploys nothing. There are two independent release channels, and a
change only reaches CI once both have been advanced and the consumer's orb pin bumped.
Two tag series - don't confuse them
| Tag | Releases |
|---|
vX.Y.Z | The source tree (github_utility/, scripts) that jobs clone at runtime |
orb/X.Y.Z | Bookkeeping mirror of a published CircleCI orb version |
The two version numbers are unrelated. Orb versions live in CircleCI, not in git -
orb/* tags are only created after the fact by orb/publish-prod-repository-tag.sh
and are not what CircleCI serves.
Why merging deploys nothing
orb/src/commands/setup-circleci-utils-and-github-token.yml clones this repo at a tag:
git clone --branch << parameters.circleci-utils-tag >> --depth 1 \
https://github.com/ethereum-optimism/circleci-utils.git /tmp/circleci-utils
circleci-utils-tag has a in that file, and that default is frozen into every
orb version. A consumer runs whatever tag its pinned orb version was published
with, no matter what says.
