Upgrading#
This page is the checklist for moving an app from one Preflight pin to the next, one released version at a time, newest first; every section follows CHANGELOG.md. Read the section for the version you are moving to, apply its steps, and verify on the next pipeline. Like a real preflight, the walk takes a few minutes and earns its keep: move the pin only after you have read the version notes.
Every input and job name a component offers is recorded in contract/inputs.json, and Preflight's build fails when a template drifts from it, so the file is the exact list of what moved. Before you move a pin, diff it between your tag and the next one (for example git diff 0.4.0 0.5.0 -- contract/inputs.json in a clone of Preflight) and check each line against that version's Breaking and Steps below. The inputs contract explains what each kind of change means for your include.
0.9.0#
Released 2026-11-12. A sixteenth component, composer-ci, one new input on proctor, the consumer a11y kit, and two
input regexes that now accept the values their own docs name. No input or job was renamed or removed. Same aircraft,
a longer checklist, and the paperwork finally matches the plane.
Breaking#
- None.
check_pathdefaults to empty, which keeps today's behavior, and both regex changes only accept more.
New: composer-ci#
The job most stack repos wrote by hand, as one include: composer install, then composer ci, and that command's exit
code decides the job. There is no allow_failure input on purpose. See
the composer-ci guide.
- component: $CI_SERVER_FQDN/enterprise-apps/preflight/composer-ci@<0.9.0 commit SHA> # 0.9.0
New: proctor check_path#
A repo that installs PROCTOR in deploy/ can run the check from the project root with check_path, so the
wayneui.copies scan sees site/assets/wayne-ui. See the proctor guide.
Fixed: config_path and php_advisory_version#
secret-detection'sconfig_pathaccepts a leading-dot path, soconfig_path: .gitleaks.toml(the name Gitleaks itself uses) no longer makes GitLab refuse the pipeline. A repo that renamed its file to dodge the old regex can rename it back.php-test'sphp_advisory_versionaccepts8.6-rcas well as8.6.0RC5.
Steps#
- Move every Preflight include to the 0.9.0 tag's full commit SHA, with
# 0.9.0in a trailing comment. - A repo with its own install-and-ci job can replace it with the
composer-ciinclude. - A repo that keeps a local a11y wrapper can copy
templates/a11y/consumer/from the 0.9.0 tag intotools/a11y/(see the a11y guide). - Nothing else changes.
How to verify#
- The pipeline is created (a refused input stops it before any job runs) and every job keeps its name.
- With
config_path: .gitleaks.toml, thesecret-detectionjob runs and reads that file.
0.8.0#
Released 2026-11-10. One new input on the portability component, session_header, for an app whose probe sign-in
route must not open for just anyone, plus a fix that makes package-publish refuse a moved version on GitLab's real
registry. No input or job was renamed or removed. The boarding pass now gets checked against the passport.
Breaking#
- None.
session_headerdefaults to empty, and an empty value sends no extra header. package-publishnow fails a release whose version is already published on GitLab from a different commit. That is the job doing what it always promised; a pipeline that passed by overwriting a version will now stop.
New: session_header#
Give it one header name and one CI variable, written Name: $VARIABLE:
session_header: "X-Portability-Token: $PORTABILITY_PROBE_TOKEN"
The probe reads the variable at run time with printenv (never eval) and sends the header on the login, same,
hop and anon requests of session-hop. It never prints the value; any message names only the header and the
variable. A value that does not match Name: $VARIABLE stops the job with an input error, and a variable that is not
set in the job flags session-hop and sends no header. Set the variable as a masked CI variable. See
the portability guide.
Steps#
- Move every Preflight include to the 0.8.0 tag's full commit SHA, with
# 0.8.0in a trailing comment. - An app whose probe sign-in route needs a secret adds
session_headerand a masked CI variable of the same name. - Nothing else changes.
How to verify#
- With
session_headerset,session-hoppasses and the job log shows the header name, never its value. - Without it, the job behaves exactly as on 0.7.0.
0.7.0#
Released 2026-11-10. One new input on the portability component, setup_command, for the step a platform runs before
it scales an app out: migrating the database. No input or job was renamed or removed. A short hop: same aircraft, one
more item on the checklist.
Breaking#
- None.
setup_commanddefaults to empty, and an empty value runs nothing.
New: setup_command#
The probe runs setup_command once, in a container of the built image named portability-setup, after any
services are up and before replica A or B starts. A non-zero exit fails the job with setup: FAIL and the last 40
lines of its output. A pass shows as setup in the job's summary. The must-fail case setup-fails proves it.
Use it with services and session-hop: a database both replicas share is empty until the app migrates it, so the
replicas' first session write fails without it. For a Laravel app:
services: [{ name: "mysql:8.4.7@sha256:<digest>", alias: db, variables: { MYSQL_ROOT_PASSWORD: "portability", MYSQL_DATABASE: "app" } }]
setup_command: php artisan migrate --force
checks: ["health", "env-only", "forwarded-headers", "logs", "sigterm", "healthcheck", "session-hop"]
Pin the service image by digest, as every Preflight default is, and point the app's DB_HOST at the alias. See
the portability guide.
Steps#
- Move every Preflight include to the 0.7.0 tag's full commit SHA, with
# 0.7.0in a trailing comment. - An app that runs
session-hopagainst aservicesdatabase addssetup_commandwith its migration command. - Nothing else changes.
How to verify#
- The portability job's summary lists
setupas passed whensetup_commandis set, and has nosetupline when it is empty.
0.6.0#
Released 2026-11-10. This release adds one component, mysql56-migrate, which proves an app's migrations on the MySQL
Citadel really runs. The portability job also runs the image's own HEALTHCHECK and can start a shared database for
session-hop. No input or job was renamed or removed. Cleared for takeoff, with one more gauge on the panel.
Breaking#
The healthcheck check is in the default checks. An include that leaves checks at its default now runs the
image's own HEALTHCHECK command inside replica A, as the app's uid, and fails when it exits non-zero three times in a
row. An image that declares no HEALTHCHECK still passes, with a note (set require_healthcheck: true to fail
instead). If your image's health command only works as root, or calls a tool the image lacks, fix the command in the
same change as the bump. An include that lists checks itself does not get the new check until you add healthcheck
to its list.
Changed#
- The portability job builds with
buildah bud --format docker, because Buildah's default OCI format dropsHEALTHCHECK. The image the probe boots is otherwise the same. - New portability inputs:
require_healthcheck(boolean, defaultfalse) andservices(array, default[], the same shape as GitLab'sservices:keyword). See the portability guide.
New: mysql56-migrate#
CREED's database rule says an app MUST run its migrations in CI against a real MySQL 5.6, because SQLite accepts DDL
that 5.6.51 rejects (a JSON column, a utf8mb4 unique index longer than 767 bytes). The component starts
mysql:5.6.51 as a service, waits for it, installs pdo_mysql (and Composer 2.11.1, when the image has none), and
runs migrate_command (default php artisan migrate --force --no-interaction).
- It carries the
amd64runner tag by default, since the official MySQL 5.6 images are amd64 only. On a GitLab with no amd64-tagged runner, settags: []on an amd64 or emulating default runner. - It runs on the default branch and tags, is manual (and allowed to fail) on merge requests, and never runs from a schedule.
- A raw PHP app passes its own migration command; the guide has both includes.
Steps#
- Move every Preflight include to the 0.6.0 tag's full commit SHA, with
# 0.6.0in a trailing comment. - If the app has migrations, add the
mysql56-migrateinclude. - If the portability job runs with the default
checks, boot the image locally and run itsHEALTHCHECKcommand as a uid with no name in group 0 before you push. - An app that keeps sessions in its database (WELD does) can now add
session-hopback: give the portability include aservicesdatabase and pointDB_HOSTat its alias.
How to verify#
- The
mysql56-migratejob is green on the default branch, and its log ends with the app's own migration output. - The portability job's summary lists
healthcheckas passed, or as passed with the "declares no HEALTHCHECK" note.
0.5.0#
Released 2026-11-09. A new component, npm-audit, the front-end half of composer-audit; a portability probe that
starts each replica the way a container runtime does, so an Apache image needs no start_command shim; a proctor job
that keeps PROCTOR's JSON report as proctor.json for Rollcall; and Composer 2.11.1 in every default. No input or job
was renamed or removed.
Breaking#
The portability launcher. The portability job now starts each replica through a launcher that gives it stdout
and stderr its uid owns and a session of its own (setsid), as a container runtime does. An include that still
carries a start_command shim calling setsid (WELD's was exec setsid bash -c '...') breaks on 0.5.0: inside the
launcher the shim forks the app away from the replica's main process, and health fails. Delete the shim in the same
change as the bump. With an empty start_command the job runs the image's own ENTRYPOINT and CMD, which is what
an Apache image (Squire's portable image, a Sourdough or WELD app) needs. A start_command that only starts the app,
with no setsid and no stdio redirect, keeps working.
Deprecated#
Nothing was deprecated in 0.5.0.
Changed#
- Composer 2.11.1. Every Composer default moves from 2.10.3 to 2.11.1: the
composer-audit,sbom,pint,phpstan,package-publishandsquire-kitimages arecomposer:2.11.1@sha256:8de2184c...(the multi-arch list digest), and php-test's and proctor'scomposer_versiondefault is2.11.1. 2.11.0 fixed GHSA-c968-33g3-wh7p and GHSA-fm2w-xgf2-f9fh, and 2.10 is no longer maintained. 2.11 drops thesource-fallbacksetting; no component sets it. An include that setsimageorcomposer_versionkeeps its own pin. - proctor keeps
proctor.json. The proctor job's artifact now keeps PROCTOR's JSON report asproctor.jsonfor 30 days, next to the Code Quality report, whether the job passed or failed. That is the file Rollcall reads withROLLCALL_PROCTOR_SOURCE=gitlab. The job adds--record "$CI_PROJECT_DIR/proctor.json"itself, and only whenproctor_commandis a plainproctor checkline and the app's PROCTOR is 0.11.0 or later. On PROCTOR 0.10.0 or older the job runs exactly as before and the runner warns thatproctor.jsonmatched no files. The proctor line's exit code still decides the job. - renovate's
dry_runpattern is on record.contract/inputs.jsonnow lists the^(null|lookup|full)$pattern the renovate template already enforced in 0.4.0, so the contract diff shows that line changed. No value that passed on 0.4.0 stops passing.
New: npm-audit#
The npm-audit component runs npm audit on the app's package-lock.json in the eslint component's Node image and
fails on an advisory at or above audit_level in a runtime dependency, then prints a full report that never fails.
It is opt-in. Its inputs and defaults:
audit_level:highby default;low,moderate,highorcritical. CREED's and Composer's wordmediumis accepted too and maps to npm'smoderate.omit_dev:trueby default, so the failing audit leaves dev dependencies out; the full report still lists them.working_dir:.by default; the directory that holdspackage-lock.json, relative to the project root.stage,job_name,imageandimage_prefix, as on the other components.
An app with no lock file (no package-lock.json or npm-shrinkwrap.json) passes with a note,
npm-audit: no lock file ... nothing to audit., so a PHP-only app never goes red. An unreachable registry fails the
job. See The npm-audit component.
Steps#
- If an include of
portabilitysets astart_commandshim that callssetsid, delete the shim (or the wholestart_commandline) in the same change as step 2. - Point each component include at the
0.5.0tag, pinned to the tag's full commit SHA with the tag in a trailing comment:
include:
- component: $CI_SERVER_FQDN/enterprise-apps/preflight/php-test@60314791565a264e97cb210813ef4f3e76512402 # 0.5.0
- Optional: add
npm-auditfor an app with a front end:
include:
- component: $CI_SERVER_FQDN/enterprise-apps/preflight/npm-audit@60314791565a264e97cb210813ef4f3e76512402 # 0.5.0
inputs:
audit_level: high
- Optional: to feed Rollcall, move the app to PROCTOR 0.11.0 or later
(
composer require --dev waynestate/proctor:^0.11).
How to verify#
The pipeline is green. The portability job passes all its checks with no shim, the composer-based jobs' Pulling docker image line names composer:2.11.1, and on PROCTOR 0.11.0 or later the proctor job's artifact holds
proctor.json. With npm-audit included, its log ends with npm audit's summary, or with the no-lock-file note.
Checklist done, doors armed: cleared for takeoff.
0.4.0#
Released 2026-11-08. Two new inputs and a Composer floor. The proctor component's git_depth (default "0") clones
the full history, so PROCTOR's override-approver check can read git blame on every override line instead of reporting
could-not-run past GitLab's 20-commit default. php-test's php_advisory_version runs one more PHP version, such as a
release candidate, in a separate job that may fail. php-test and proctor refuse a composer_version older than 2.9.6,
the floor with the 2026 security fixes.
Breaking#
An include that sets composer_version on php-test or proctor to a version older than 2.9.6 no longer starts: GitLab
rejects the input before the pipeline runs. The default (2.10.3) is unaffected, and no other input, default or job
name changed.
Deprecated#
Nothing was deprecated in 0.4.0.
Steps#
- If an include sets
composer_versionbelow 2.9.6, remove the input (the default is 2.10.3) or set 2.9.6 or later. - Point each component include at the
0.4.0tag, pinned to the tag's full commit SHA with the tag in a trailing comment:
include:
- component: $CI_SERVER_FQDN/enterprise-apps/preflight/php-test@87d9b6fc6b0ed302dd729986525282cd7b567ebd # 0.4.0
- Optional: on a very large repository, set the proctor component's
git_depthto a number such as50; override lines older than that then report could-not-run. To hear about the next PHP early, set php-test'sphp_advisory_version, for example8.6.0RC2.
How to verify#
The pipeline is green, the proctor job log's fetch line no longer says git depth set to 20 (unless you set
git_depth), and with php_advisory_version set a php-test-advisory job runs and may fail without failing the
pipeline.
0.3.1#
Released 2026-11-08. Every component that installs packages caches under a fixed key per component (such as preflight-pint, or preflight-php-8.4 for one PHP version of php-test) instead of a lock-file hash, and saves its cache even when the job fails. A lock change, or a retry after a dropped download, fetches only what is missing.
Breaking#
0.3.1 has no breaking changes: inputs, defaults and job names are the same as in 0.3.0.
Deprecated#
Nothing was deprecated in 0.3.1.
Steps#
Point each component include at the 0.3.1 tag, pinned to the tag's full commit SHA with the tag in a trailing comment:
include:
- component: $CI_SERVER_FQDN/enterprise-apps/preflight/php-test@b90323b5823287a7840095d0d5f0682aaeedf327 # 0.3.1
The first pipeline on the new pin fills the new cache keys, so expect it to download everything once.
How to verify#
The pipeline is green, and a component's job log shows Creating cache preflight- followed by the component's key, and, after a failed job, Saving cache for failed job.
0.3.0#
Released 2026-11-08. Docker Hub images now come through the group's Dependency Proxy by default (a new image_prefix input), and more components cache their Composer and npm downloads.
Breaking#
Every component whose image comes from Docker Hub (proctor, php-test, composer-audit, sbom, pint, phpstan, eslint, secret-detection, package-publish, renovate, squire-kit) now pulls image_prefix/image, and image_prefix defaults to your group's Dependency Proxy (${CI_DEPENDENCY_PROXY_GROUP_IMAGE_PREFIX}). image keeps its default and is the path after the prefix. Only an app that overrides image, or runs where the proxy is off, needs to act:
- If the override was
${CI_DEPENDENCY_PROXY_GROUP_IMAGE_PREFIX}/<image>only to reach the proxy, delete theimage:input; the default does the same. Keeping it puts the prefix in twice, and the pull fails. - If it names a different Docker Hub image, drop the
${CI_DEPENDENCY_PROXY_GROUP_IMAGE_PREFIX}/part and keep the rest. - If it names another registry, move the host and path into
image_prefixand keep the rest inimage. - On a GitLab or group without the proxy, set
image_prefix: docker.io.
a11y (mcr.microsoft.com) and portability (quay.io) have no image_prefix and are unchanged: the proxy serves Docker Hub only.
Deprecated#
Nothing was deprecated in 0.3.0.
Steps#
-
Move every Preflight include to the
0.3.0tag in one change, pinned to the tag's full commit SHA with the tag in a trailing comment, and remove any proxiedimage:input in the same change (step 1 above):include: - component: $CI_SERVER_FQDN/enterprise-apps/preflight/php-test@23038dfe767f6ef60e3b2efca1128f53d9acdff7 # 0.3.0Before:
- component: $CI_SERVER_FQDN/enterprise-apps/preflight/php-test@<old SHA> # 0.2.0 inputs: image: ${CI_DEPENDENCY_PROXY_GROUP_IMAGE_PREFIX}/php:8.4-cli-trixie@sha256:<digest>After:
- component: $CI_SERVER_FQDN/enterprise-apps/preflight/php-test@23038dfe767f6ef60e3b2efca1128f53d9acdff7 # 0.3.0 inputs: image: php:8.4-cli-trixie@sha256:<digest> -
On a GitLab or group without the Dependency Proxy, add
image_prefix: docker.ioto each Docker Hub include'sinputs. -
A mirrored package moves the SHA in its GitHub workflow (
.github/workflows/ci.yml) to the same commit.
Verify: the job log's Pulling docker image line shows the prefix once, and each job's first line (Preflight component <name> ...) shows the new ref and sha. See Dependency caching.
0.2.0#
Breaking#
The portability component is now one job, portability (named by a new job_name input), instead of portability-build and portability-run, and it checks what ADR-0010 asks for instead of the goss list. It builds the image with Buildah and runs it in the same job, so nothing is pushed to the container registry and no app image is pulled. Only an app that already includes portability from 0.1.4 needs to act:
buildah_imageis renamedimage(same default, the Buildah image pinned by digest); the oldimageinput (the app image) is gone.start_commandis optional: empty runs the image's ownENTRYPOINTandCMD, the way the platforms do. Keep it only if your image needs a different start.- New inputs with defaults:
job_name,build_args,runtime_paths,port_env,env,stop_timeout,probe_path,identity_header,session_login_path,session_check_path,logs_pathandchecks. Setenvto what the app needs to boot (secrets from CI/CD variables), and either add a test sign-in route forsession-hopor leave it out ofchecks. - Anything that waited on
portability-runwithneeds:now namesportability. - The app image needs no curl, sha256sum or tar any more; the probe runs outside it.
See The portability component for the six checks and how to fix each failure.
Changed#
The Buildah image default (now the portability component's image input) moved from the plain version tag to the immutable tag quay.io/buildah/stable:v1.43.5-immutable@sha256:7c2b605262748ace2c5c57c5550942d0adad57aec82ede3070927722306c0ffb: Red Hat re-pushed the plain version tag and garbage-collected the old digest, so a pipeline pinned to it broke. If your app overrides it, point it at an -immutable tag pinned by digest too.
The composer-audit component gains an abandoned input (fail, report or ignore) for how composer audit treats abandoned packages. No action needed: the default is fail, which is what the component already did, so existing pipelines behave exactly as before.
A new a11y component checks a site's pages with axe-core in Playwright (WCAG 2.1 AA by default; add wcag22aa for 2.2 AA). It is opt-in: add its include to start the gate, with allow_failure: true while the site fixes its first findings. See The a11y component. Preflight's own local gate (scripts/a11y.sh, scripts/a11y.ps1) now runs the component's checker, at 320 px instead of 360 px, with the reflow check; tools/a11y/ is gone.
A new squire-kit component fails the pipeline when a Squire deploy kit drifts from the Squire release its .squire.json records (squire init --check). It is opt-in: run vendor/bin/squire init --check --path=deploy first, clean up what it reports, then add the include with working_dir: deploy. See The squire-kit component.
The Renovate preset no longer updates files inside a Squire kit (docker-compose.squire.yml and .squire/**, outside Squire's own templates/): those bumps made every kit drift. Its Squire rule now runs squire update on the kit in the merge request it opens for a new Squire. The runner must allow those commands: set squire_kit_tasks: true on the runner project's renovate include. Until it does, each Squire merge request shows an artifact error and needs vendor/bin/squire update --path=deploy run by hand, as before. See Squire kits.
This release needs GitLab 18.7 or later: every component now declares spec: component: and prints a Preflight component line as its first command, and GitLab accepts that spec key only from 18.7 on. On an older instance, pipeline creation fails on the unknown key, so upgrade GitLab or pin an older Preflight tag.
0.1.4#
Released 2026-11-03. The new pieces are opt-in: the portability component, a job_name input on every component except portability, and a stricter Renovate preset.
Breaking#
0.1.4 has no breaking changes: the version adds a component, an input and preset rules, and removes nothing.
Deprecated#
Nothing was deprecated in 0.1.4.
Steps#
Point each component include at the 0.1.4 tag, pinned to the tag's full commit SHA with the tag in a trailing comment:
include:
- component: $CI_SERVER_FQDN/enterprise-apps/preflight/proctor@79029cc2300702d0d450c42cc699e12af1b731f8 # 0.1.4
A mirrored package pins the same SHA in its GitHub workflow:
jobs:
ci:
uses: waynestate/preflight/.github/workflows/php-package.yml@79029cc2300702d0d450c42cc699e12af1b731f8 # 0.1.4
Adopt the new pieces when you want them:
portability: it ships in 0.1.4 and later (0.1.3 does not include it), so pin the0.1.4tag, or the full commit SHA of a commit at or after it. The build job needs a runner that permits user namespaces (Buildah uses unshare for its storage); the run job needs only the project's container registry and an app image that carries curl, sha256sum and tar.job_name: it ships in 0.1.4, so pin 0.1.4 or a SHA at or after that release. Set it when one project includes the same component more than once, for example in a monorepo with two apps; without it the two jobs would share a name and merge into one.- Renovate preset: component version bumps now really wait for review instead of auto-merging (the component-rule manager name is
gitlabci, matching repository deps), and a bump of the recorded Squire kit version carries thesquire-kitlabel and never auto-merges; a person runssquire updateto refresh the kit files.
How to verify#
Push the change and run the app's pipeline. The components are ordinary jobs, so they run whenever the app's pipeline runs; expect the same jobs as before, green. PROCTOR's preflight-pinned check warns when an include is not pinned to a commit SHA. If you added portability, the portability-run job passes only when the image boots the strict way and the goss checks hold.
0.1.3#
Released 2026-11-03. Two consumer-facing changes: the proctor component installs the app with --no-plugins --no-scripts, and the shared Renovate preset stopped auto-merging the pins that every pipeline runs.
Breaking#
0.1.3 has no breaking changes, but the proctor job now installs the app's dependencies with composer install --no-plugins --no-scripts, so the app's plugins and scripts never run inside the job.
Deprecated#
Nothing was deprecated in 0.1.3.
Steps#
Bump each component include to the 0.1.3 tag's full commit SHA, with the tag in a trailing comment:
include:
- component: $CI_SERVER_FQDN/enterprise-apps/preflight/proctor@<full commit SHA> # 0.1.3
If your group runs the shared Renovate preset, read the two behavior changes before you merge the bump:
- Updates inside
templates/**,contract/**and.gitlab-ci.yml, and bumps of a Preflight component version in an app'scomponent:include, no longer auto-merge: they carry theneeds-reviewlabel and wait for a person. - The
renovatecomponent no longer setsRENOVATE_TOKENandGITHUB_COM_TOKENfrom themselves in the jobvariables:; on GitLab 19.5 that self-reference arrived as literal text and shadowed the masked project CI/CD variables, so the job now reads both tokens straight from the project.
How to verify#
Run the pipeline and confirm the jobs run on the new pin. In the runner project, confirm the job reads RENOVATE_TOKEN straight from the project as a masked CI variable, and that a bump touching the templates, the contract or a component include pin opens a merge request labeled needs-review instead of auto-merging.
0.1.2#
Released 2026-10-29. The site gained the agent-ready kit (prompt blocks, Markdown twins, llms.txt) from Squire, and the proof page moved to a private site that needs a Wayne State sign-in.
Breaking#
0.1.2 has no breaking changes: the version touches the site, the README and the proof page, not the components.
Deprecated#
Nothing was deprecated in 0.1.2.
Steps#
Bump each component include to the 0.1.2 tag's full commit SHA, with the tag in a trailing comment:
include:
- component: $CI_SERVER_FQDN/enterprise-apps/preflight/proctor@<full commit SHA> # 0.1.2
How to verify#
Run the pipeline and confirm the component jobs run on the new pin. PROCTOR's preflight-pinned check warns when an include is not pinned to a commit SHA.
0.1.1#
Released 2026-10-29. Two new components: package-publish, which publishes a semantic version tag to the GitLab group's built-in Composer registry, and renovate, with the shared preset renovate/default.json. The reusable GitHub Actions workflow for mirrors ships in this tag too.
Breaking#
0.1.1 has no breaking changes: the version adds components and changes only the repository's own PHPStan config.
Deprecated#
Nothing was deprecated in 0.1.1.
Steps#
Bump the existing includes to the 0.1.1 tag's full commit SHA, and add the new components where you want them:
include:
- component: $CI_SERVER_FQDN/enterprise-apps/preflight/package-publish@<full commit SHA> # 0.1.1
inputs:
group_id: "<your group id>"
group_id is required: the numeric id of the GitLab group whose built-in Composer registry hosts the package.
A package mirrored to GitHub calls the reusable workflow from its own .github/workflows/ci.yml; the workflow ships in the 0.1.1 tag, so pin the full commit SHA of the release tag and keep the tag in a trailing comment:
name: CI
on:
push:
branches: ['**']
tags: ['v*', '*.*.*']
jobs:
ci:
uses: waynestate/preflight/.github/workflows/php-package.yml@<full commit SHA> # 0.1.1
How to verify#
Run the pipeline. For package-publish, the job runs only on tags and reads the registry first: a version already published from this commit passes quietly, and a version published from a different commit fails the pipeline. For a mirrored package, a release tag is not done until it is green on both sides.
0.1.0#
Released 2026-10-27. First tagged release.
Breaking#
0.1.0 is the first tagged release, so there is nothing to break: it is the baseline every later pin moves from.
Deprecated#
Nothing was deprecated in 0.1.0.
Steps#
Include the components pinned to the 0.1.0 tag's full commit SHA:
include:
- component: $CI_SERVER_FQDN/enterprise-apps/preflight/proctor@<full commit SHA> # 0.1.0
How to verify#
Run the pipeline and confirm the component jobs run on the pin.
Related#
- Changelog: the raw entries this page is built from.
- Install: the requirements, the include snippet, and how to verify the pipeline picked the component up.
- Updating image pins: why the pins are digests and how to look one up.
- Renovate: what auto-merges, what waits, and what the runner project owes.
- Troubleshooting: symptoms, causes and fixes.
- Overview: what Preflight is and where the manual starts.