v4.17.0 - Summer '25 Release
After taking a much-needed break from open source work, the v4.17.0 release is finally ready!
Managed Package Release - v4.17.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.16.0 and v4.17.0 for the managed package by reviewing:
- The v4.17.0 milestone to see all of the issues & pull requests that are included in the this release.
- The diff between v4.16.0 and v4.17.0 to see all of the code & metadata changes that have been committed since the last managed package release.
Managed Package Enhancements & Bugfixes
- ✅Release
v4.16.5- Capture Apex Cursor Transaction Limits by @vikashkrml in PR #892 → closed issue #760 - 🐞Release
v4.16.4- Bugfix: logger LWC Initialization Message by @jongpie in PR #884 → fixed issue #870 reported by @dominykasvitkus - ✅Release
v4.16.3- Made LogBatchPurger's Batch Size Configurable` by @jongpie in PR #880 → closed issue #807 reported by @halderanindya - ✅Release
v4.16.2- Origin Location Stacktrace Parsing Improvement by @jamessimone in PR #872 - ✅Release
v4.16.1- Data Masking & String Truncation Improvements by @jongpie in PR #866 → fixed issue #695 reported by @itague
Core Unlocked Package Release - v4.17.0
These changes are new for both the unlocked package and the managed package.
Summer '25 Release Upgrade
- Bumped all metadata to API
v64.0(Spring '26 release)- Also updated the list of picklist values in several 'API version' picklist fields on
Log__candLogEntry__c
- Also updated the list of picklist values in several 'API version' picklist fields on
Apex Logging Bugfixes
- Updated
Loggerto more accurately reflect the current quiddity value when logging the system messageLogger - Saving X log entries via <quiddity> - Fixed #910 - Updated
CallableLoggerto useList<String>instead ofList<Object>for tags passed in via OmniStudio- Previously using
List<Object>caused some exceptions, and the values should always be strings anyway
- Previously using
JavaScript Logging Bugfixes
- Updated
loggerLWC to reflect the latest changes in Salesforce's JavaScript stack traces- These changes broke the previous stack trace parsing logic - hopefully the modified logic is more resilient to future changes
- The Jest tests in
logger.test.jshave also been expanded to include parsing examples of stack traces from Chrome, Firefox, Edge - with & without debug mode (which can make a difference in the stack traces & parsing logic)
- Updated
loggerLWC to immediately instantiate an internal instance ofLoggerService- This was previously done in
connectedCallback, which added an extra unnecessary event cycle that could cause some occasional goofiness
- This was previously done in
PrismJS Enhancements & Bugfixes
- Upgraded the version of PrismJS in
LoggerResourcesstatic resource from1.29.0to1.30.0 - Updated some CSS in
loggerCodeViewer.cssto correct some rendering issues due to changes in SLDS + SLDS v2 - Fixed #777 - Corrected an issue in
loggerCodeViewerthat caused PrismJS's line highlighting to not work correctly when only 1 instance ofloggerCodeViewer(used by other LWCs likelogEntryMetadataViewer) was on a page
LWC Testing Improvements
- Fixed #881 - Added more Jest tests in to the LWCs tests below to validate existing functionality that wasn't previously covered by tests:
logEntryEventStream.test.jslogEntryMetadataViewer.test.jsloggerHomeHeader.test.jslogger.test.jsloggerPageSection.test.jsloggerSettings.test.jslogViewer.test.js
- Added a
recipesLWCloggerWrapperto mimic orgs that use Nebula Logger'sloggerLWC through their own logging LWC
Apex Testing Improvements
- Updated
LogEntryEventHandler_Teststo only use mock CMDT records (instead of relying on the metadata records deployed to the org)- All other test classes were previously updated to only use mock records, but this particular test class was overlooked
- Partially addressed #922 - Updated pipeline-only tests in
LogEntryEventHandler_Tests_FieldMappings.clsto validate that custom picklist fields with restricted values are handled properly
Pipeline Changes
- Updated scratch org definition files to tweak how OmniStudio is enabled in scratch orgs
- Updated pipeline & local dev scripts to use OmniStudio managed package v258.6 (Winter '26 release)
- Upgraded some dev dependencies in
package.json
Installation Info
Core Unlocked Package - no namespace
Full Changelog: v4.16.5...v4.17.0
- SF CLI:
sf package install --wait 20 --security-type AdminsOnly --package 04tg70000000rNhAAI - Sandbox: https://test.salesforce.com/packaging/installPackage.apexp?p0=04tg70000000rNhAAI
- Production: https://login.salesforce.com/packaging/installPackage.apexp?p0=04tg70000000rNhAAI
Core Managed Package - Nebula namespace
Full Changelog: v4.16.0...v4.17.0
- SF CLI:
sf package install --wait 20 --security-type AdminsOnly --package 04tg70000000r5xAAA - Sandbox: https://test.salesforce.com/packaging/installPackage.apexp?p0=04tg70000000r5xAAA
- Production: https://login.salesforce.com/packaging/installPackage.apexp?p0=04tg70000000r5xAAA