Skip to content

chore: release (release) - 8.19.1#5375

Merged
jhefferman-sfdc merged 2 commits intoreleasefrom
release-release-2-8.19.1
May 16, 2025
Merged

chore: release (release) - 8.19.1#5375
jhefferman-sfdc merged 2 commits intoreleasefrom
release-release-2-8.19.1

Conversation

@jhefferman-sfdc
Copy link
Contributor

Details

release 8.19.1

Does this pull request introduce a breaking change?

  • 😮‍💨 No, it does not introduce a breaking change.

Does this pull request introduce an observable change?

  • 🤞 No, it does not introduce an observable change.

GUS work item

W-18539058

* chore: add tests, centralize coverage
* chore: add stubs for unimplemented v2 exports
* chore: simplified shadow test
* fix: gate protection, review comments, malformed context handling
* fix: doc review
@jhefferman-sfdc jhefferman-sfdc requested a review from a team as a code owner May 16, 2025 16:34
@salesforce-nucleus
Copy link
Contributor

✅ All Pre-release Checks Passed

  • Check PR user has rights to execute the workflow
    PR owner is allowed to initiate release/deploy
  • Check PR is approved
    PR 5375 is approved
  • Check PR is mergeable
    PR 5375 is mergeable
  • ⚠️ Check GUS reference is present
    PR does not contain a reference to a GUS work item. You can update it any time by including '@W-XXXXXXX' into the title or body of the PR
  • Check no conflicting Github release
  • Check NPM packages have not been released yet
  • ⚪️ Check Maven artifacts have not been released yet (skipped)
    Skipping check since project doesn't deliver Maven artifacts
  • ⚪️ Check GAV mapping exists for jar repo (skipped)
    Skipping GAV mapping check because a core jar is not being released.

@salesforce-nucleus
Copy link
Contributor

🚢 Release Starting

This pull request has been merged and the release of version 8.19.1 is starting.

You can monitor the progress of the release in Nucleus by visiting the following URL.
https://nucleus.uipengsys-public.buildndeliver-s.aws-esvc1-useast2.aws.sfdc.cl/workflows/268451

@jhefferman-sfdc jhefferman-sfdc merged commit 107a414 into release May 16, 2025
12 of 17 checks passed
@jhefferman-sfdc jhefferman-sfdc deleted the release-release-2-8.19.1 branch May 16, 2025 17:01
@anuragoyar
Copy link

Potential Risks and Suggestions

No specific issues found that require inline comments. The changes appear to be a version bump from 8.19.0 to 8.19.1 across the LWC framework with the addition of new context-related functionality.

Summary:

This PR represents a minor version update (8.19.0 to 8.19.1) of the Lightning Web Components (LWC) framework with the following key changes:

  1. New Context API Implementation:

    • Added a new context system that allows components to establish contextual relationships within the component tree
    • Introduced setContextKeys, setTrustedContextSet, and related methods to manage context
    • Added support for context providers and consumers in the component tree
  2. File Changes:

    • Version bumps across all LWC packages
    • New implementation files for context functionality
    • New test files for context functionality
    • Documentation updates in README.md files
    • Updates to renderer implementations to support context
  3. Test Coverage:

    • Added comprehensive hydration tests for the new context functionality
    • Added unit tests for the context implementation

The changes are well-structured and include proper test coverage for the new functionality. The context API appears to be designed as an experimental feature that is only enabled when the ENABLE_EXPERIMENTAL_SIGNALS feature flag is set.

Deployment Considerations:

This appears to be a safe update as:

  1. The version change is minor (8.19.0 to 8.19.1)
  2. The new context functionality is behind a feature flag (ENABLE_EXPERIMENTAL_SIGNALS)
  3. The changes don't modify existing behavior but add new capabilities
  4. Test coverage is comprehensive with both unit and integration tests
  5. The bundlesize limit has been slightly increased to accommodate the new functionality

The PR is suitable for production deployment as it follows proper versioning practices and includes appropriate test coverage. The new functionality is opt-in through feature flags, which minimizes the risk of unexpected behavior in existing components.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants