v4.17.0 - Summer '25 Release (API v64.0)

[jongpie]

Core Unlocked Package Changes

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__c and LogEntry__c

Apex Logging Bugfixes

• Updated Logger to more accurately reflect the current quiddity value when logging the system message Logger - Saving X log entries via <quiddity>
• Updated CallableLogger to use List<String> instead of List<Object> for tags passed in via OmniStudio
  • Previously using List<Object> caused some exceptions, and the values should always be strings anyway

JavaScript Logging Bugfixes

• Updated logger LWC 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.js have 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 logger LWC to immediately instantiate an internal instance of LoggerService -
  • This was previously done in connectedCallback, which added an extra unnecessary event cycle that could cause some occasional goofiness

PrismJS Enhancements & Bugfixes

• Upgraded the version of PrismJS in LoggerResources static resource from 1.29.0 to 1.30.0
• Updated some CSS in loggerCodeViewer.css to correct some rendering issues due to changes in SLDS + SLDS v2
• Fixed an issue in loggerCodeViewer that caused PrismJS's line highlighting to not work correctly when only 1 instance of loggerCodeViewer (used by other LWCs like logEntryMetadataViewer) was on a page

LWC Testing Improvements

• Added more Jest tests in to the LWCs tests below to validate existing functionality that wasn't previously covered by tests:
  • logEntryEventStream.test.js
  • logEntryMetadataViewer.test.js
  • loggerHomeHeader.test.js
  • logger.test.js
  • loggerPageSection.test.js
  • loggerSettings.test.js
  • logViewer.test.js
• Added a recipes LWC loggerWrapper to mimic orgs that use Nebula Logger's logger LWC through their own logging LWC

Apex Testing Improvements

• Updated LogEntryEventHandler_Tests to 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
• Updated pipeline-only tests in LogEntryEventHandler_Tests_FieldMappings.cls to 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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.60%. Comparing base (c1402a9) to head (2ae273f).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #925      +/-   ##
==========================================
+ Coverage   91.55%   93.60%   +2.05%     
==========================================
  Files          58       58              
  Lines        6322     6302      -20     
  Branches      199      199              
==========================================
+ Hits         5788     5899     +111     
+ Misses        514      401     -113     
+ Partials       20        2      -18     

Flag	Coverage Δ
Apex	92.92% <100.00%> (-0.05%)	⬇️
LWC	96.18% <100.00%> (+10.05%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.