NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #1308 by repository stars
Latest stable
v0.83.0
Last release 1 years ago
31 Oct 2025
Ships on a steady schedule
a new release about every 8 days
Most releases are documented
notes for 44 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
2 years old
190 releases · first in 2025
Drag across the ruler to compare, or tap a release to open it.
Add updated at and created at order for vendor
### Added - Add SOA generator - Show last assessment date
Add link dialog for measure evidences
Your coding agent can read these notes before it upgrades. Set up the MCP server →
### Added - Add forgot password pages
Pagination for people, vendors, documents, data and assets
Fix filedrop upload too small file size
Fix framework view too many queries
Nothing published for this version
- Fix measure count
Fix 5xx on document count for risk
### Fixed - Fix API path contain undefined
Fix localhost enforce at build time
Add backend fulltext search on controls, documents, risks and measures
totalCount field in Connection objectNothing published for this version
Prevent publishing of document versions with no changes
Add title and owner id to document versions
Added sort key updated_at for vendors
updated_at for vendors### Changed - Change policies to documents ### Added - Add type to documents ### Fixed - Fix HIPAA import
Add url input type for vendor assessement
Add automatic vendor assessment
Nothing published for this version
Fix missing position field migration
position field migrationRename severity into risk score
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
### Fixed - Fix http cache etag - Fix cannot delete measure
Nothing published for this version
Enable HTML support in Markdown renderer
While a sample is open, each page reports a page view, and cookies already listed on the banner are still reported
category_granted, and the batch includes
consent_action when the visitor has one. The grant follows current
consent for the matching tracker. A * in the pattern is a glob: an
exact name wins, and otherwise the match with the longest fixed text
wins. Necessary categories are always granted, and an unmatched name
uses the banner's default for non-necessary trackersdocument.cookie and named storage writes (for example localStorage[key] = value) are classified as SCRIPT instead of HTTP or PRE_EXISTING. Hooks start
document.cookie and named storage writes (for example
localStorage[key] = value) are classified as SCRIPT instead of
HTTP or PRE_EXISTING. Hooks start before the config fetch, and the
leftover cookie scan waits for the config so inventoried cookies are
not re-queued on every page loadnull or reporting NaN for numbers, and convert the key
only onceNothing published for this version
New vendors in the built-in lists
Cookie detections report the cookie Domain, and a richer observation replaces an earlier one without demoting its source
Domain, and a richer observation
replaces an earlier one without demoting its sourceMax-Age that does not fit a 32-bit
integer instead of failing the whole batchFix 5xx when invite user in an organization
### Fixed - Evidence URL not set
re-resolves the banner root on click so a header control that mounts before the banner still reopens preferences
<probo-settings-link> re-resolves the banner root on click so a
header control that mounts before the banner still reopens preferencestc field keeps the stored
category grants instead of projecting deny-allTCFRuntime.onUIVisible so a TCF addon can follow banner /
panel / privacy-choices open and closeprojectConsentFromTCF maps TCF purpose consent/LI bits onto category
slugs (AND, fail-closed). Customize and TC restore use it when TCF is ontcf (cmp_id, cmp_version,
publisher_cc, and a publisher-filtered IAB gvl) when the hidden
capability is on; the key is omitted otherwise. This replaces the
flat tcf_enabled, tcf_vendors, and gvl_version fields from
0.18.0tc field on probo_consent when a TCF runtime is
registered via setTCFRuntime. Encoding and __tcfapi live in
@probo/cookie-banner-tcf so this package stays IAB-freetc with consent records and restores it from GET visitor consent
onto probo_consent and getTCFRuntime()?.onConfig so returning visitors
keep __tcfapi after a cookie misssetLayoutRenderer,
setTCFRuntime, bootCookieBanner, and layout primitives (floatingCard,
esc, BRANDING, CLOSE_ICON). The themed banner asks a registered
renderer first and falls back to opt-in / opt-out / notice<probo-preference-panel> requires only probo-save-button, so addons can
replace the category list. .panel-body and .toggle-group style the
replacement controls//Fix typo mesure instead of measure
Fix typo mesure instead of measure
BannerConfig exposes the TCF fields tcf_enabled, tcf_vendors, and gvl_version, plus a new exported TCFVendor type describing each disclosed IAB Global
BannerConfig exposes the TCF fields tcf_enabled, tcf_vendors, and
gvl_version, plus a new exported TCFVendor type describing each
disclosed IAB Global Vendor List vendorAPI calls to the retired hosted console hosts (eu.console.getprobo.com, us.console.getprobo.com) are rewritten to eu.probo.com and us.probo.com so exi
eu.console.getprobo.com, us.console.getprobo.com) are rewritten to eu.probo.com and us.probo.com so existing snippets keep working after the domain migration. Self-hosted and already-migrated base URLs are unchanged.Nothing published for this version
google-consent-mode="off" (and data-google-consent-mode="off" on the script tag) disables the Google Consent Mode integration entirely, for sites that
google-consent-mode="off" (and data-google-consent-mode="off" on the script tag) disables the Google Consent Mode integration entirely, for sites that already manage Consent Mode through their own CMP or GTM setup### Fixed - Fix SQL syntax error
Operators can disable resource detection per banner: the SDK skips ResourceDetector and the server ignores resources on the shared report endpoint, wh
ResourceDetector and the server ignores resources on the shared report endpoint, while cookies and storage keep reporting normallyimportance field from measure as it's not used anymoreNothing published for this version
Privacy Choices wording keys are regulation-scoped: privacy_choices_* → privacy_choices_*_ccpa, falling back to the unsuffixed key for configs that ha
privacy_choices_* → privacy_choices_*_ccpa, falling back to the unsuffixed key for configs that have not migrated. The compact opt-out CTA stays on button_opt_out (generic); California receives the statutory label from the server via button_opt_out_ccpaFix psql generated_gid returns padded base64
generated_gid returns padded base64user_id not set when create new organizationadditional_email_addresses not set when invite in organizationNothing published for this version
Regulation is a string alias rather than an exhaustive union, so the SDK no longer mirrors every backend regulation identifier. Banner behavior is dri
Regulation is a string alias rather than an exhaustive union, so the SDK no longer mirrors every backend regulation identifier. Banner behavior is driven by the server-provided layout, and new jurisdictions (US state laws, Canadian provincial PIPA) no longer require an SDK releaseCCPA Privacy Choices panel (privacy_choices state + ): under CCPA, the settings link opens a dedicated surface that describes the right to opt out of
privacy_choices state + <probo-privacy-choices>): under CCPA, the settings link opens a dedicated surface that describes the right to opt out of sale/sharing and the right to limit sensitive personal information, with a Do Not Sell or Share action (11 CCR § 7015). SPI is explained as a statement in v1 (no toggle)<probo-settings-link> always shows the statutory “Your Privacy Choices” label plus the official CPPA opt-out icon under CCPA (overriding integrator children); otherwise keeps children or falls back to aria_cookie_settings; optional GPC badge when the opt-out preference signal was applied<probo-settings-link> is present (warn + probo-validation), since it is the sole reopen controllayout object in the banner config (presentation, initial_state, reopen_state, default_non_necessary_granted, buttons, settings_link). The banner now renders from these explicit fields instead of inferring behavior from hardcoded regulation checks and empty text keys. A config without layout means a self-hosted Probo backend older than probod v0.246.0 (the first release that sends it): the client logs an error asking to update probod and falls back to a strict opt-in layoutACKNOWLEDGE consent action (via <probo-acknowledge-button> / client.acknowledge()) rather than ACCEPT_ALL, so the audit trail reflects an acknowledgement<probo-cookie-banner> is now a thin dispatcher that mounts a focused renderer per presentation (opt-in / opt-out / notice); each renderer owns only its own markup, wording keys, and quirks, replacing the single component's runtime button-togglingresolveLayout and resolveBannerText (plus the BannerLayout / BannerText / Presentation types) so headless integrators can resolve the active presentation and its wordinglayout.reopen_state is privacy_choices (not the compact opt-out banner). Other OPT_OUT regimes (PIPEDA, LGPD) still reopen the compact banner1emlayout rather than regulation === "CCPA" / consent_mode branchinglayout.presentation; the server-side key remap is now a shim for pre-0.12 clients only. Headless integrators on 0.12+ should use resolveBannerText / layout to render the correct copy<probo-settings-button> widget and the reopen-widget attribute — place <probo-settings-link> in the header or footer instead (breaking)New vendors in the built-in vendors list
New vendors in the built-in vendors list
Nothing published for this version
Fix grammar for "people" in the navigation bar
Rename "Mitigation" in "Mesure"
Added business owner and security owner fields to vendors
New risk treatment strategy options: Mitigate, Accept, Avoid, Transfer
One column per month.