v4.17.0 - Summer '25 Release #949
jongpie
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
After taking a much-needed break from open source work, the
v4.17.0release is finally ready!Managed Package Release -
v4.17.0This 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.0andv4.17.0for the managed package by reviewing:Managed Package Enhancements & Bugfixes
v4.16.5- Capture Apex Cursor Transaction Limits by @vikashkrml in PR Fix #760: Capture Apex cursor limits #892 → closed issue Capture Apex cursor limits #760v4.16.4- Bugfix: logger LWC Initialization Message by @jongpie in PR Bugfix: logger LWC Initialization Message #884 → fixed issue Disabling system messages in LWC component #870 reported by @dominykasvitkusv4.16.3- Made LogBatchPurger's Batch Size Configurable` by @jongpie in PR Made LogBatchPurger's batch size configurable #880 → closed issue Apex heap size too large during purging after 30 days #807 reported by @halderanindyav4.16.2- Origin Location Stacktrace Parsing Improvement by @jamessimone in PR Origin Location Parsing Improvement #872v4.16.1- Data Masking & String Truncation Improvements by @jongpie in PR Data Masking & String Truncation Improvements #866 → fixed issue Text truncation does not always properly truncate (especially when combined with data masking rules) #695 reported by @itagueCore Unlocked Package Release -
v4.17.0These changes are new for both the unlocked package and the managed package.
Summer '25 Release Upgrade
v64.0(Spring '26 release)Log__candLogEntry__cApex Logging Bugfixes
Loggerto more accurately reflect the current quiddity value when logging the system messageLogger - Saving X log entries via <quiddity>CallableLoggerto useList<String>instead ofList<Object>for tags passed in via OmniStudioList<Object>caused some exceptions, and the values should always be strings anywayJavaScript Logging Bugfixes
loggerLWC to reflect the latest changes in Salesforce's JavaScript stack traceslogger.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)loggerLWC to immediately instantiate an internal instance ofLoggerServiceconnectedCallback, which added an extra unnecessary event cycle that could cause some occasional goofinessPrismJS Enhancements & Bugfixes
LoggerResourcesstatic resource from1.29.0to1.30.0loggerCodeViewer.cssto correct some rendering issues due to changes in SLDS + SLDS v2loggerCodeViewerthat caused PrismJS's line highlighting to not work correctly when only 1 instance ofloggerCodeViewer(used by other LWCs likelogEntryMetadataViewer) was on a pageLWC Testing Improvements
logEntryEventStream.test.jslogEntryMetadataViewer.test.jsloggerHomeHeader.test.jslogger.test.jsloggerPageSection.test.jsloggerSettings.test.jslogViewer.test.jsrecipesLWCloggerWrapperto mimic orgs that use Nebula Logger'sloggerLWC through their own logging LWCApex Testing Improvements
LogEntryEventHandler_Teststo only use mock CMDT records (instead of relying on the metadata records deployed to the org)LogEntryEventHandler_Tests_FieldMappings.clsto validate that custom picklist fields with restricted values are handled properlyPipeline Changes
package.jsonInstallation Info
Core Unlocked Package - no namespace
Full Changelog: v4.16.5...v4.17.0
sf package install --wait 20 --security-type AdminsOnly --package 04tg70000000rNhAAICore Managed Package -
NebulanamespaceFull Changelog: v4.16.0...v4.17.0
sf package install --wait 20 --security-type AdminsOnly --package 04tg70000000r5xAAAThis discussion was created from the release v4.17.0 - Summer '25 Release.
Beta Was this translation helpful? Give feedback.
All reactions