Summer '24 Release (API v61.0) - v4.14.0

[jongpie]

Core Unlocked Package Changes

• Bumped all metadata to API v61.0 (Summer '24 release)

  • Also updated the list of picklist values in several 'API version' picklist fields

• Resolved Make Log and Log Entry page tabs conditionally visible based on logged data #697 by updating LogEntryRecordPage and LogRecordPage flexipages to conditionally display tabs (tab-visibility functionality was added in Salesforce's Summer '24 release)

  • Also eliminated the tab "Database Result Details" on LogEntryRecordPage & consolidated its contents to instead be part of the tab "Related Records". This keeps all of the fields related to SObject data grouped together.

• Added 5 new list views on LogEntry__c

  1. All Exception Log Entries

  2. All HTTP Request Log Entries

  3. All HTTP Response Log Entries

  4. All REST Request Log Entries

  5. All REST Response Log Entries

     

• Deprecated the formula field LogEntry__c.LoggingLevelWithImage__c, and reverted to only using LogEntry__c.LoggingLevel__c. The emojis shown in LoggingLevelWithImage__c have now been added to the labels of the picklist values in the global value set LoggingLevel.

  • ⚠️ Existing list views have been updated to use LoggingLevel__c, which will automatically be changed for orgs upgrading versions of the unlocked package. But for orgs using the managed package, the list views will not be automatically updated, you will need to manually update the list views' selected fields (if desired).

• Fixed assertion failure for it_should_return_user_search_results_list_when_matches_found test method #688 by updating LoggerSettingsController_Tests to call LogManagementDataSelector.getInstance().getUsersByNameSearch(), instead of duplicating the query

• Updated the descriptions of the 4 included permission sets to clarify what each one provides

• Code cleanup (internal use only): Updated public instance method LogEntryEventBuilder.setTimestamp() to use a fluent API, and streamlined the existing usages of setTimestamp() in several other classes by updating to use the fluent API

Pipeline & Dev Changes

• Fixed a flaky pipeline integration test in nebula-logger/extra-tests/tests/LogEntryEventHandler_Tests_FieldMappings.cls
• Added some sf CLI environment variables to build.yml to disable checking for updates during pipeline runs
  • The sf CLI is periodically upgraded in the repo, there's no need for the pipeline to check during every run
• Added new scratch org def file config/scratch-orgs/dev-scratch-def.json that will only be used for development (not in the pipeline or when creating package versions)
  • It includes the feature 'EinsteinGPTPlatform', which I've been trying out when writing Apex. But there's no need for this feature when creating package versions & I want to avoid somehow accidentally creating any kind of dependency on this feature.
  • Also renamed the existing scratch def files to have a 'build-' prefix to clarify their purpose vs the (new) dev def file
• Added new path to sfdx-project.json for nebula-logger/dev/ to store some extra metadata that's used during dev. This metadata doesn't impact Nebula Logger directly & is not included in Nebula Logger's packages
  • This new path is now the default in sfdx-project.json for creating/retrieving new metadata
• Added a .mob file to the project root - this provides some defaults when using the mob CLI with Nebula Logger
  • Using the mob CLI isn't necessary at all for working on Nebula Logger, but I sometimes like to use it during development of prototypes

[Ben-Nathan-CTM]

With all due respect is there any specific date on the release?

[jongpie]

@Ben-Nathan-CTM I am currently collaborating with a few teams/companies to try to finalize the scope of changes that will be included in v4.14.0 - there are a few features that I'm hoping to include, but I'm trying to get feedback first before finalizing things. Testing the managed package is also quite tedious, as there are several aspects that I need to manually validate before releasing any changes. My hope is to have this released in the next week or two.

[codecov]

Codecov Report

Attention: Patch coverage is 90.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 95.37%. Comparing base (7a715d1) to head (dd94d11).

Files	Patch %	Lines
...ore/main/logger-engine/classes/ComponentLogger.cls	83.33%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #700      +/-   ##
==========================================
- Coverage   95.39%   95.37%   -0.02%     
==========================================
  Files          51       51              
  Lines        5645     5648       +3     
==========================================
+ Hits         5385     5387       +2     
- Misses        260      261       +1     

Flag	Coverage Δ
Apex	95.37% <90.00%> (-0.02%)	⬇️

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.