Releasing#
Release Drawbridge in five steps, from the changelog to the tag that publishes the gateway image.
The steps#
- Move the lines under the top heading of
CHANGELOG.md(Keep a Changelog) to## X.Y.Z (YYYY-MM-DD), and setVersion::CURRENTinsrc/Version.phptoX.Y.Z: the CLI prints it and/metricsreports it, andVersionTestfails until the two agree. composer ciand the rig green locally, then both pipelines green for that commit.- Run a secrets scan of the history and check that nothing internal (server names, people, tenant or client IDs) is in the tree.
- Tag
X.Y.Z(nov) on git.wayne.edu. The tag runsgateway-image:publish, which pushes the image to the stack's image registry: the group'simagesproject, repositorydrawbridge-gateway, at the registry theNOUGAT_REGISTRYproject variable names, logging in with theNOUGAT_REGISTRY_USERandNOUGAT_REGISTRY_TOKENdeploy token (protected variables, so release tags must be protected). - A release needs a maintainer's approval. Running it in front of real apps also needs the Citadel platform team.
The front page#
The front page is not part of this release. site/ is the static front page, served on Citadel through a small raw-PHP deploy/ layer generated with Squire. The gateway itself is a separate deploy.
Who maintains it#
Wayne State University Enterprise Applications maintains Drawbridge. For the internal runbook (accounts, the app registration, secret storage, platform contacts), ask Enterprise Applications.
What has shipped#
What has shipped, with dates, is in the Changelog; this page states no release date or number beyond it.