Skip to content

Deployment & Release Process

This page covers how updates are shipped to Agend Product Suite products. For Agend Pro's WordPress/Kinsta release cadence, see Agend Pro — Updates & Maintenance.

Release Cadence

Agend Product Suite ships on a continuous integration / continuous deployment (CI/CD) pipeline. New features are released on a frequent cadence — currently weekly, rather than Agend Pro's monthly cycle, reflecting the faster iteration pace of the underlying platform.

Bug Fixes & Security Updates

Bugs and security issues are not batched into the weekly feature release. They are triaged and deployed as needed, using the same severity-driven approach already applied across Agend products:

  • Fixes are prioritised based on the severity of the issue (using CVSS scoring), whether it affects your specific configuration, and the potential impact on your members' experience.
  • High-severity issues with a known exploit are deployed as a priority fix outside the regular release cadence, rather than waiting for the next weekly release.

This mirrors the priority-fix policy documented for Agend Pro in Updates & Maintenance — applied here against a continuous-deployment pipeline rather than a staging/production monthly rollout.

Release Process

Every change passes through code review and automated test, type-check, and lint gates before it is deployed — see Platform Security for how this fits into our broader security posture.

In progress

A fully documented customer-facing change-communication policy (e.g. release notes, advance notice for breaking changes) is still being finalised for Agend Product Suite. This page will be updated once that's published.

Questions about our release process can be directed to security@agend.com.au.