Changelog

This page lists Compliance Glossary for Confluence releases, newest first. Each entry gives the version number, the release date, and what changed for users.

We ship updates regularly. Install the app to receive update notifications via Atlassian Marketplace.

v6.9.0 24 October 2026

• Archive import shows its result — an invalid or changed archive shows “Archive validation failed:” with its error codes, a parity mismatch shows an error, and a valid archive shows the imported record count with confirmed parity. The file picker accepts JSON archives only.
• CSV import lists skipped rows — the preview counts rows without a term name or definition, and Import Complete lists each one by row number. If no row is valid, the error names the rows to fix.
• Enterprise freezes keep the Term Owner — new freezes record each approved term’s Term Owner role. Freezes made before this release have no owner.
• Uploaded evidence keeps its retention date — the artifact record stores the retention class, retention date, a legal-hold flag (always off for uploads), and deletion and archive state. The app records these values; it does not enforce retention or delete evidence.

v6.8.0 24 October 2026

• Platform update — All app dependencies updated to their latest versions, including React 19 and the Forge bridge and resolver libraries. No change to features or stored data.

v6.7.0 24 October 2026

• Platform and security update — Forge SDK dependencies updated and published security advisories in bundled libraries fixed. No change to features or stored data.

v6.6.0 14 October 2026

• Git findings show the latest scanned revision only — after a clean scan of a newer commit, findings from older revisions no longer appear as current.
• Evidence workspace keeps its place — the trace graph and verification results reload without resetting the workspace.

v6.5.0 14 October 2026

• Git connector available in production — install the Compliance Glossary for Confluence GitHub App (read-only Contents and Metadata), connect a repository and select Scan by request.
• Remediation Queue shows one row per finding — a term used several times on one page appears once with a mention count, and status filters no longer show stale rows.

v6.4.0 14 October 2026

• HIPAA starter pack — 21 terms for the HIPAA Privacy, Security and Breach Notification rules, 15 quoted from 45 CFR 160.103, 164.304 and 164.402, plus a Requirements Mapper catalog.
• Resolve findings from the Remediation Queue — a Resolve button opens the finding, so you no longer need a new scan to acknowledge, justify or close it. The queue filter also matches the rule (deprecated, unapproved, pending_review, synonym, undefined_term).
• AI-assisted curation and definition fit fixed — candidate generation and the usage definition-fit check failed in production; both work again. Terms used on more than three pages no longer fail curation.
• Clearer failure logging — every failure records content-free details for support.

v6.3.0 13 October 2026

• EU AI Act pack follows the Digital Omnibus — Article 3 definitions as amended by Regulation (EU) 2026/1744: amended “safety component” (14), new “SME” (14a) and “small mid-cap enterprise” (14b). The pack now has 70 terms; reinstalling adds the new terms as drafts, and approved terms are not changed automatically.

v6.2.0 13 October 2026

• Re-approval on meaning changes — editing the name, definition, synonyms or effective dates of an approved term sends it back to review, and another person must approve it again
• Trace node pickers and review queues show artifact titles instead of internal IDs
• Fix: backward (provenance) trace now follows links in the correct direction

v6.1.0 12 October 2026

• Baseline sign-off — each reviewer records an in-app attestation with their role, bound to the baseline content fingerprint
• Baseline package download — terms, meanings, effective dates, pages, versions, hashes and sign-offs as JSON and CSV
• Baseline compare — diff two baselines and download a change note for controlled reissue
• Term change impact — list the pages that use a changed term
• Trace nodes and links with four-eyes approval; export one trace chain for an auditor or supplier
• Terms: effective dates, parent terms, and a warning when you edit a term frozen in the current baseline
• PDF text extraction for uploaded evidence
• Fixes: audit CSV column alignment, Forge storage reliability, safer Word/Excel/PDF parsing, wider GDPR erasure coverage

v6.0.0 26 September 2026 · major upgrade

• Enterprise baselines — freeze approved terminology and exact Confluence page revisions in one governed package, with historical meanings, hashes, usage observations, findings, coverage and trace links
• Bidirectional traceability — trace forward from requirements to documents, code and tests, or backward from implementation to its root reason
• Change impact across every indexed artifact affected by a changed term or requirement
• Baseline integrity verification without changing frozen evidence
• Content-addressed evidence archive: export, validate and re-import
• Artifact glossary slices and controlled-reissue handoffs
• Word, Excel, PDF, text and CAD evidence upload through authenticated, hash-verified ingestion up to 25 MiB
• Adds Forge SQL and Object Store; existing administrators may need to approve the major upgrade. The optional GitHub connector means this version is not eligible for Runs on Atlassian.

v5.0.0 – v5.1.0 19–20 August 2026

• Audit evidence package — scope, scans, page status, findings, resolutions, and print-to-PDF export
• Page status: passed, needs attention, stale, not checked
• Finding ownership, due dates, severity, resolution reason, and closure evidence
• Term owners, review dates, expiry, and reapproval status; positive usage evidence for approved terms
• Optional GitHub connector for report-only scans of approved repositories and paths, with “Add as draft” from Git terminology findings
• Requirements mapping conflict detection
• Optional admin-triggered Forge LLM curation that creates draft candidates only; human approval remains required

v4.4.0 – v4.7.0 22 June – 5 August 2026 · maintenance releases

• Minor updates published on Atlassian Marketplace between v4.3.0 and v5.0.0

v4.3.0 15 April 2026 · marketplace release

• Approved and published on Atlassian Marketplace (ECOHELP-123535, 15 April 2026)
• Bulk approve — select terms in review and approve them in batch (shipped 5 April)
• Context-aware bulk actions — only valid status transitions shown per filter (shipped 5 April)
• Dashboard screenshot refreshed to reflect current UI (5 April)

v4.2.0 5 April 2026

• Deep code review — DRY refactoring across backend and admin UI (4 review passes, 26 fixes)
• ALCOA+ Attributable + Contemporaneous — every term edit records actor (contentEditedBy) and ISO-8601 timestamp; audit-trail write failures now surface a warning instead of being silently dropped
• Test count expanded from 69 to 77 automated tests (formula-injection sanitization, CRLF, trailing-comma, null/undefined input)
• Scanner performance — scanPage uses cached term lookup (~200ms vs ~7.5s)
• Forge KVS upgraded to 1.6.0 with strict schema validation (findingsTruncated, contentEditedBy declared)
• ESLint + pre-commit hook + CI lint — automated code-quality gates on every commit and PR
• Major dependency upgrade — React 18, Atlaskit css-reset 7, Forge API/KVS/Bridge, Babel, Jest 30, ESLint 10

v4.1.0 29 March 2026

• Dependabot configured for daily dependency updates, aligned with Atlassian SLAs
• Telegram notifications for Dependabot PRs and security audit failures
• npm audit fix — resolved brace-expansion and yaml moderate vulnerabilities
• Forge KVS bumped 1.4.0 → 1.5.0; @babel/preset-env 7.29.0 → 7.29.2; jest 30 / babel-jest 30 / eslint 10

v4.0.0 25 March 2026 · privacy & security hardening

Resolves Atlassian Marketplace review feedback on the v2.5.0 submission of 21 March 2026. Renumbered from the v2.x line to mark the privacy/security baseline used for the live listing.

• Resolver calls migrated from asApp() to asUser() for correct permission scoping
• Customer DPA, security policy, sanitized error logging, security.txt
• Security audit + tests CI pipeline (push, PR, weekly cron); undici upgrade for high-severity fix
• "How It Works" page documenting scanner logic and architecture

v2.5.0 21 March 2026 · first marketplace submission

• Initial submission to Atlassian Marketplace review (paid app licensing plumbing, ToS rewrite with indemnification + €100 minimum liability cap, GDPR-aligned privacy policy)
• Dark theme toggle, space selector dropdown, AI support chatbot
• Bug fixes: double-encoded CQL in user search, external links in Forge iframe, phantom audit records in bulk operations, resolution badge crash on missing theme

v2.0.0 – v2.4.0 10–20 March 2026 · internal iterations

• Internal-only iterations between MVP and first Marketplace submission. Includes 8 enterprise-scale fixes from expert audit (20 March), code review hardening, and audit-trail integrity work.

v1.0.0 (MVP) 10 March 2026 · internal pre-release

• Term management, compliance scanner, audit export
• Four-eyes approval workflow with change justification and stale-approval detection
• Version history with full audit trail
• CSV import/export, search, roles, error handling
• Enterprise-scale scanner — pre-compiled regex, fast-reject, paginated INDEX (63 tests at this point)

Note on numbering: the app does not embed a semantic version in source. Version labels above (v1.x–v4.x) reflect the Marketplace-side version assigned to each submitted bundle. Internal v3.x bundles were not separately submitted — the next Marketplace-visible submission after v2.5.0 was v4.0.0.

Related

Compliance for Confluence — approved terms, page scanning, and audit evidence for regulated teams in Confluence

Security whitepaper — Forge architecture, SOC2/DORA/NIS2/GDPR/FDA 21 CFR Part 11 posture

Compliance guide — what auditors check and how Compliance Glossary maps to real regulatory standards

Documentation — installation, admin UI, four-eyes workflow, scanner, CSV import/export

AI Act terminology governance — Article 3 definitions managed as a versioned glossary

DORA terminology — ICT risk, third-party, and incident taxonomy for financial-entity teams