Changelog

Every ReleaseGuard release

What shipped, when, and why it matters. Updated with every version.

Rule-level configuration dialog

Fine-grained control per document and release type — applicability, up-versioning behaviour, ID and history rules, and the required-by-stage gate.

  • New modal for editing a rule directly from the documentation matrix grid.
  • Applicability (required / conditional / not applicable) per document and release type.
  • Up-version behaviour options: up-version existing, new doc, or leave untouched.
  • Doc ID rule (same ID + new version, or new ID) and history requirement toggle.
  • Required-by-stage selector (DEV / VAL / PROD) with inline reminder.
  • Optional guidance field travels with the rule so authors see the same expectation.

Release dossier with signature manifest

One-click ZIP export containing approved file revisions, the signature manifest, the release audit CSV, and SHA-256 checksums.

  • Dossier export includes every approved file revision at its final state.
  • Signature manifest in PDF lists author, reviewer, QA approver, and stage signatures with timestamps.
  • Release audit trail exported as CSV (append-only record of every action).
  • Checksum file (SHA-256) for every revision included in the dossier.
  • Manifest marked preliminary until the release reaches Released status.

Matrix change requests with three-party approval

Changing a product's matrix now requires separate approvals from Manager, QualityManager, and ProductOwner.

  • Administrators can request a matrix change on an existing product.
  • Request maps each open release to a release type in the new matrix.
  • Requester cannot approve their own request; one person cannot provide multiple approvals.
  • Any required approver can reject with a reason; Administrator can withdraw.
  • After all three approvals, changes are applied to the product and its open releases.
  • Release in a promotion stage returns to In Progress when its checklist changes.

Nine-stage release lifecycle with hard gates

Release lifecycle formalised into Planning → In Progress → Ready for DEV → DEV Deployed → Ready for VAL → VAL Deployed → Ready for PROD → PROD Deployed → Released, with three hard gates.

  • Document gate re-checked at every promotion action.
  • QA approver signing a gate must differ from the deployment recorder.
  • Stage signatures and evidence comments are append-only and audit-trailed.
  • A release in a promotion stage can be returned to documentation work with a reason, or cancelled.
  • Deployments recorded manually with reference and evidence in a signed action.

SHA-256 file integrity and password re-entry

Every upload fingerprinted; approval refused if the file changes after submission. Approval-type actions require password re-entry.

  • Files fingerprinted with SHA-256 at upload time.
  • Review and approval refused if the current file fingerprint differs from submission.
  • Password re-entry required for approval-type actions with a recorded meaning.
  • Signatures capture user, time, action, and relevant file fingerprint.
  • Uploaded files, signatures, and audit records protected against editing or deletion through application controls and database triggers.

Excel import and export for documentation matrices

Download a blank workbook or import a completed one. Older three-column workbooks still accepted.

  • Blank Excel template available from New Documentation Matrix.
  • Import on a new matrix or on an existing draft.
  • Each release type has three rule values plus a Required by stage value.
  • Workbooks validated before changes are applied.
  • Importing into an existing draft replaces its release types and rules.
  • Older three-column workbooks accepted and use QA-recommended document-name defaults.

Product defaults and bulk assignment

Configure default author, reviewer, and QA approver per product; fill empty assignments in one action.

  • Product page supports default author, reviewer, and QA approver.
  • Optional document-type overrides per role.
  • Defaults applied to new releases; role membership and separation-of-duties rules checked.
  • Bulk-assign selected documents on a release.
  • Apply product defaults to fill only empty assignments.
  • Assignment changes are audit-trailed.

Role-aware dashboard and notification bell

Dashboard surfaces what matters to your roles; notifications link to the source of the action.

  • Dashboard shows active releases, promotion progress, and work assigned to you.
  • Pending applicability decisions surfaced with a count.
  • QA approvals and reviews relevant to your roles listed in dedicated panels.
  • Notification bell with unread count; each notification links to its related item.
  • Mark all as read to clear the unread list.
  • Overdue work may also appear in a daily digest, depending on configuration.

Initial release

Documentation matrices, role-separated workflows, and append-only audit trails.

  • Documentation matrices with rules per release type.
  • Role model: Administrator, ReleaseManager, Author, Reviewer, QAApprover, Manager, QualityManager, ProductOwner.
  • Document workflow: Decision pending → Not Started → Draft → In Review → Reviewed → Approved.
  • Electronic signatures with password re-entry.
  • Audit trail exportable as CSV or PDF.
  • Lockout after five failed sign-in attempts; sessions expire after 30 minutes of inactivity.
  • No self-registration — accounts provisioned by administrators.