Skip to content
Menu

Releasing#

Release Drawbridge in five steps, from the changelog to the tag that publishes the gateway image.

The steps#

  1. Move the lines under the top heading of CHANGELOG.md (Keep a Changelog) to ## X.Y.Z (YYYY-MM-DD), and set Version::CURRENT in src/Version.php to X.Y.Z: the CLI prints it and /metrics reports it, and VersionTest fails until the two agree.
  2. composer ci and the rig green locally, then both pipelines green for that commit.
  3. Run a secrets scan of the history and check that nothing internal (server names, people, tenant or client IDs) is in the tree.
  4. Tag X.Y.Z (no v) on git.wayne.edu. The tag runs gateway-image:publish, which pushes the image to the stack's image registry: the group's images project, repository drawbridge-gateway, at the registry the NOUGAT_REGISTRY project variable names, logging in with the NOUGAT_REGISTRY_USER and NOUGAT_REGISTRY_TOKEN deploy token (protected variables, so release tags must be protected).
  5. 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.