Changelog¶
The base SDK and SessionReplay are released under the same NuGet version, with changes recorded separately. Native/vcpkg and the Electron Adapter use their own version numbers; Native's optional Replay feature is delivered with the same port version.
Guance.Windows¶
0.1.0-alpha.11 (2026/10/19)¶
- Browser RUM in WebView2 now includes
sdk_pkg_info, recording the page Browser SDK version viaweb; the host SDK identity remains unchanged. - Fixed an issue where the Browser RUM Bridge depended on the Replay switch. Browser RUM can now be integrated normally even when Replay is disabled or optional components are not installed.
- Fixed an issue where newlines in string fields could split reported records, and prevented the SDK's own upload requests from being repeatedly collected as Resources.
- Added
GetUploadQueueDiagnosticsSnapshot()to check the number of pending RUM and Log writes and the Replay queue status.
0.1.0-alpha.9 (2026/10/07)¶
- Removed the Replay implementation from the base package while retaining the existing configuration, recording control, and privacy APIs. Existing Replay applications must add the same version of
Guance.Windows.SessionReplaywhen upgrading. - Added a client-side
IsSessionReplayAvailableto determine whether the optional component is actually available. When the component is missing, version-mismatched, or fails to load, diagnostics are output while regular RUM, Log, and Trace continue to work; WebView2 declares therecordscapability only when the component is actually available. - The base package and SessionReplay are packaged and released under the same version. See the separate Version Information below for the Replay component's features.
0.1.0-alpha.7 (2026/08/15)¶
- .NET RUM and Log Intake requests now have compression enabled by default; it can be disabled with
CompressIntakeRequests = false. - Fixed the Deflate request body format in .NET and the bundled Native runtime, now using zlib wrapping that complies with
Content-Encoding: deflate.
0.1.0-alpha.6 (2026/08/13)¶
- Added persistent anonymous user identifiers isolated by RUM application ID. Unauthenticated users remain consistent after process restarts, and RUM and Log data are automatically correlated.
- The bundled Native runtime now automatically collects cold start and warm start Actions by default.
- RUM and Log Intake requests in the bundled Native runtime use Deflate compression by default.
- Fixed an issue where Session Replay could upload segments lacking an associated View ID.
0.1.0-alpha.4 (2026/08/12)¶
- Added
GuanceConfig.DataModifierandGuanceConfig.LineDataModifierto modify tags and fields of RUM, Log, and Resource data before caching. - Added
RumPrivacyConfig.CaptureHttpHeadersandRumPrivacyConfig.RedactedHeaderNamesto collect HTTP request and response headers on demand and redact sensitive headers. - Added
GuanceConfig.DiagnosticListener,GuanceSdk.AddDiagnosticListener(...), andGuanceSdk.GetDiagnosticsSnapshot()for local configuration and runtime state troubleshooting. GuanceClient.StartAction(..., bool needWait, ...)andGuanceSdk.StartAction(..., bool needWait, ...)now support explicitly waiting for completion. Actions now uniformly include high-frequency call protection, View switch completion, and a maximum 5-second duration limit.- Windows crashes, app unresponsiveness, and network errors now consistently use the RUM error classification and field structure.
- Privacy rules are now consistently applied after application data modifiers.
0.1.0-alpha.2 (2026/08/09)¶
- Added automatic Trace propagation, application startup tracking, and Logging data reporting capabilities.
- Added a shared desktop Sample configuration and additional public API integration examples.
- Added experimental Session Replay validation support for WPF, WinForms, WinUI 3, and Electron Samples.
- Strengthened solution-level NuGet packaging, Native runtime assets, and consumer-side validation.
- Extended bounded cache, diagnostics, privacy, and upload configuration APIs.
0.1.0-alpha.1 (2026/08/09)¶
- First release of the experimental Guance Windows observability SDK.
- Added managed APIs for RUM, distributed tracing, logs, upload scheduling, and bounded file caching.
- Provides Windows x86, x64, and ARM64 Native runtime assets.
- Supports WPF, WinForms, WinUI 3, WebView2, and Electron integration.
- Added experimental Session Replay capability, which is disabled by default and can be enabled on demand.
View the Guance.Windows source changelog
Guance.Windows.SessionReplay¶
0.1.0-alpha.11 (2026/10/19)¶
- Precisely depends on the same version of
Guance.Windows, working with the base SDK to query the Replay queue status for pending encoding and persistence.
0.1.0-alpha.9 (2026/10/07)¶
- First release of a standalone optional NuGet package that contains the managed Replay recording, encoding, persistence, and upload implementation, with a precise dependency on the same version of
Guance.Windows. - The existing configuration, recording control, and privacy APIs continue to be used through the base SDK. Installation does not automatically enable Replay; you still need to explicitly enable the configuration and recording. Replay remains experimental.
- It continues to use the base SDK's Session correlation, sampling, and privacy configuration. When the component is unavailable, the base SDK outputs diagnostics and continues regular RUM, Log, and Trace.
- This package does not include the Native Replay DLL; C/C++ and Electron use the optional runtime provided by the Native/vcpkg versions below.
View the Guance.Windows.SessionReplay source changelog
Guance.Windows.Native¶
0.1.0-alpha.11 (2026/10/19)¶
- Fixed an issue introduced in
0.1.0-alpha.10after splitting the Replay component: full snapshots and incremental records of Browser Session Replay forwarded by the Electron Bridge were rejected, causing Replay segments to fail to upload. Session identifiers continue to be managed uniformly by the Native Core. - When upgrading Electron Full Mode with Replay, update the base Native runtime and the Replay supplemental component at the same version and architecture; Mixed Mode requires updating the host's
guance-windows-native[replay]dependency. The Replay fix itself does not require changes to the npm Adapter JavaScript or the NuGet managed Replay implementation. - Added
sdk_pkg_infoin conjunction with npm Adapter0.1.0-alpha.6: host RUM/Log recordselectron, Browser RUM/Log additionally recordswebwhen the version is available, with the same rule in Full Mode and Mixed Mode.
0.1.0-alpha.10 (2026/10/07)¶
Base Native SDK¶
- The base DLL has removed the Replay implementation while retaining the existing C configuration and control interfaces. If you only use RUM, Log, and Trace, installing the base port is sufficient.
- Added
guance_rum_is_session_replay_available(); when the component is missing or cannot be loaded, Replay is disabled with diagnostics while regular RUM, Log, and Trace continue to work.
Session Replay Feature¶
- The
replayfeature of the same port installs a separate Replay DLL. The base DLL loads the component from the same directory on demand and validates the module ABI and SDK version. - The Replay DLL must keep the same version and architecture as the base DLL. Existing Replay applications need to select this feature when upgrading, and Replay must still be explicitly enabled after installation.
Electron Windows Runtime¶
- This version delivers base runtime and Replay supplemental archives for x64, x86, and ARM64 separately, six archives in total, along with corresponding checksum files.
- Both Full Mode and Mixed Mode Bridges declare Replay capability based on configuration and actual component availability;
recordsis not declared when components are missing. In Mixed Mode, the Replay component is provided by the host'sreplayfeature.
0.1.0-alpha.7 (2026/08/15)¶
- Fixed the Deflate format of Native RUM and Log Intake requests, now using zlib wrapping that complies with
Content-Encoding: deflate.
0.1.0-alpha.6 (2026/08/13)¶
- Native RUM and Log Intake requests use Deflate compression by default, with new
compress_intake_requeststoggle andflush_interval_msperiodic flush configuration. - Added persistent anonymous user identifiers isolated by RUM application ID, which remain consistent after process restarts and are reused by Native and Electron telemetry.
- Native and Electron integrations automatically collect cold start and warm start Actions by default; this can be disabled with
enable_app_launch_trackingorenableAppLaunch. - Session Replay no longer uploads segments lacking an associated View ID.
0.1.0-alpha.5 (2026/08/12)¶
- Added an optional
electron-adaptervcpkg feature that installs the SDK-provided Electron Main Process and Preload public entry points for mixed-mode applications. - Added an in-process Electron Bridge Server C API that writes Browser telemetry data to an app-held Native SDK handle.
- Added Browser Log and experimental Browser Session Replay forwarding in both Full Mode and Mixed Mode of the Electron Adapter.
- The
electron-bridgevcpkg feature now installs the Electron Adapter, Bridge EXE, and matching Native runtime together. - The enabled state and privacy level of Electron Session Replay are uniformly determined by the Native Bridge capability. When Native Replay is disabled, the
recordscapability is no longer declared and Replay input is rejected.
0.1.0-alpha.4 (2026/08/12)¶
- Added
guance_rum_start_action_ext(..., int need_wait)to create Native RUM Actions that require explicit completion. - Native Actions now uniformly include high-frequency call protection, View switch completion, and a maximum 5-second duration limit.
- Native crash and app unresponsive events now consistently use the RUM error classification and field structure.
- Added
guance_sdk_get_version()to read the release version compiled into the Native runtime; RUM, Log, and Session Replay data report this version viasdk_version. - Added
guance_sdk_write_electron_bridge_line(...)to write validated Browser RUM, launch, error, Log, and Replay Bridge messages to an app-held SDK handle. - Added
guance_rum_add_launch_action_ext(...)to associate a launch Action with an existing Browser View. - The Electron Bridge now has Session identifiers managed uniformly by the Native Core and no longer accepts Browser-side Session overrides.
- The Electron cold start Action waits for and associates with the first primary Browser View within a limited time; if no View appears, it falls back on timeout.
0.1.0-alpha.3 (2026/08/11)¶
- Added
guance_configure_data_modifiers(...)to modify tags and fields of Native RUM and Log data before caching. - Added optional HTTP request and response header collection, with configurable redaction of sensitive headers.
- Added an optional
electron-bridgevcpkg feature to installguance_windows_electron_bridge.exeand its Native runtime dependencies. - URL and HTTP header privacy rules are now uniformly applied after application data modifiers.
- Native Resource completion events can carry request and response headers, with privacy filtering performed inside the SDK.
0.1.0-alpha.2 (2026/08/09)¶
- Added Native Crash and UI Hang monitoring, with support for resuming reporting at the next launch.
- Added automatic WinHTTP Trace propagation and Resource auto-collection capabilities.
- Added a Native Console integration Sample and expanded the public C/C++ SDK header files.
- Strengthened Native packaging, CMake, release tag, and vcpkg registry validation.
- Expanded Electron Native Bridge and experimental Session Replay diagnostics.
0.1.0-alpha.1 (2026/08/07)¶
- First release of the experimental Windows x64 dynamic library.
- Provides stable C ABI interfaces for RUM, distributed tracing, logging, Native monitoring, and diagnostics.
- Provides installable
GuanceWindowsNativeCMake package andGuance::WindowsNativetarget. - Provides a bounded file queue that does not depend on the default SQLite.
- Added experimental Session Replay capability, which is disabled by default and can be enabled on demand.
View the Guance.Windows.Native source changelog
Electron Native Adapter¶
0.1.0-alpha.6 (2026/10/19)¶
- Windows Full Mode and Mixed Mode automatically provide the npm Adapter version to the Native Core for
sdk_pkg_info.electron; Browser RUM and Browser Log keep the page SDK version forweb. - The default Native Runtime for Windows x64, x86, and ARM64 has been updated to
vcpkg_0.1.0-alpha.11, and the optional Replay supplemental component uses the same version and architecture. The macOS default remains1.6.8-alpha.6.
0.1.0-alpha.5 (2026/10/07)¶
- Added Windows Replay supplemental component installation to
@cloudcare/electron-native-adapter, supporting--with-replay,--replay-archive, and corresponding postinstall environment variables. - The installer validates the version, architecture, source, and file hashes of the base and Replay manifests;
stageWindowsRuntime()also copies the installed Replay DLL andreplay-manifest.jsonoutside the ASAR. - In the published npm package, the default SDKs are
vcpkg_0.1.0-alpha.8on Windows and1.6.8-alpha.6on macOS. When using0.1.0-alpha.10and later split-package versions, Full Mode requires explicitly selecting the corresponding Native SDK and installing the matching Replay supplemental component before enabling the configuration. - In Mixed Mode, the C++ host provides the Replay component, and the Adapter decides whether to forward recorded data based on the Bridge's actual capability. When the component is missing, regular RUM continues to work.
View the Electron Native Adapter source changelog
Pre-release Versions
alpha and beta versions are not covered by stability or compatibility guarantees. NuGet projects should pin verified package versions; vcpkg projects should pin the SDK registry baseline to avoid implicit upgrades during builds.