Skip to content

v4.19.0 - Spring '26 Release

Choose a tag to compare

@jongpie jongpie released this 03 Aug 14:18
· 6 commits to main since this release
bb9a0ba

Managed Package Release - v4.19.0

This release is for both the unlocked package (as always), as well as the managed package! You can see everything that's changed between v4.18.0 and v4.19.0 for the managed package by reviewing:

  • The v4.19.0 milestone to see all of the issues & pull requests that are included in the this release.
  • The diff between v4.18.0 and v4.19.0 to see all of the code & metadata changes that have been committed since the last managed package release.

Managed Package Enhancements & Bugfixes

Core Unlocked Package Changes - v4.19.0

These changes are new for both the unlocked package and the managed package, with the exception of the changes to the plugin framework (available only in the unlocked package).

Spring '26 Release Upgrade

  • Bumped all metadata to API v66.0 (Spring '26 release)
    • Also updated the list of picklist values in several 'API version' picklist fields on Log__c and LogEntry__c
  • Also retrieved all metadata after the API upgrade, which resulted in some (minor) changes to several XML metadata files

Optimizations

  • Added a custom index on LogEntry__c.Timestamp__c to help speed up queries, list views, etc.

LWC Improvements

  • Fixed a bug in loggerCodeViewer that (unintentionally) stripped out angle-bracketed code when showing Apex code snippets on the LogEntry__c flexipage (see screenshot below)
    • The previous approach used for rendering code with PrismJS was causing any code snippet containing < and > (like List<SomeClass> and Map<String, Object>) to be parsed by the browser as HTML, which was stripped out/ignored, resulting in the code snippet displayed being incorrect. Everything should render correctly now 🥳
image

Apex HTTP & REST Request/Response Improvements

  • Fixed #1007 by updating LogEntryEventBuilder to, finally, properly truncate all of the string fields for HTTP & REST request & response data. All of the text fields referenced within these 4 methods should now be properly truncated:
    • setHttpRequestDetails()
    • setHttpResponseDetails()
    • setRestRequestDetails()
    • setRestResponseDetails()
  • Resolved #982 with 2 changes:
    1. Updated the LogEntry__c list view AllRestResponseLogEntries to also include LogEntry__c records with RestResponseStatusCode__c >= 0 (list views don't let you filter on not-null for number fields 😠 )
    2. Update the LogEntry__c flexipage LogEntryRecordPage to show the Apex REST Response section if the LogEntry__c record has RestResponseStatusCode__c >= 0 (this is the same logic used in the list view)

Trigger Handler Bugfix

  • Fixed a small-but-important issue in the trigger handler framework internally used by Nebula Logger - disabled LoggerSObjectHandler__mdt records are now (intentionally) queried so that disabling the corresponding trigger handler works correctly

Plugin Framework Changes (Unlocked Package Only)

  • Marked a few more fields on LoggerPlugin__mdt as deprecated - they've been deprecated/unused for a while, but there were still some lingering references within the repo. These fields (listed below) will be fully removed from the unlocked package in the future - doing so may break existing versions of any plugins, so the full deprecation will be done in a future release.
    • LoggerPlugin__mdt.ExecutionOrder__c
    • LoggerPlugin__mdt.PluginApiName__c
    • LoggerPlugin__mdt.PluginType__c
    • LoggerPlugin__mdt.SObjectType__c

Installation Info

Core Unlocked Package - no namespace

Full Changelog: v4.18.4...v4.19.0

Core Managed Package - Nebula namespace

Full Changelog: v4.18.0...v4.19.0