search

salesforce / sfdx-lwc-jest

Run Jest against LWC components in SFDX workspace environment
MIT License
162 stars 81 forks source link

chore: bump the lwc group across 1 directory with 6 updates #378

Closed dependabot[bot] closed 3 weeks ago

dependabot[bot] commented 1 month ago

Bumps the lwc group with 6 updates in the / directory:

Package From To
@lwc/compiler 6.7.2 7.0.1
@lwc/engine-dom 6.7.2 7.0.1
@lwc/engine-server 6.7.2 7.0.1
@lwc/module-resolver 6.7.2 7.0.1
@lwc/synthetic-shadow 6.7.2 7.0.1
@lwc/wire-service 6.7.2 7.0.1

Updates @lwc/compiler from 6.7.2 to 7.0.1

Release notes

Sourced from @​lwc/compiler's releases.

v7.0.1

What's Changed

Full Changelog: https://github.com/salesforce/lwc/compare/v7.0.0...v7.0.1

v7.0.0

LWC v7.0.0 contains breaking changes. Please read carefully below if you are upgrading from v6.

If you are upgrading from v5, please upgrade to v6 first.

[!NOTE] LWC v7 corresponds to Salesforce release Winter '25 (API version 62).

New features

Summary of breaking changes

Breaking changes

[!NOTE] On the Salesforce Lightning platform, this change only applies to components with an API version of 62 or above.

Class object binding is a new feature that makes it more ergonomic to render class attributes in your LWC components. As part of this feature, class rendering has changed for some uncommon use cases.

If you are using a dynamic class in your template:

... (truncated)

Commits
  • 35ebe60 chore: release v7.0.1 (#4333)
  • 1a83a8d chore: release v7.0.0 (#4309)
  • c0423f5 refactor(template-compiler): move implicit stylesheet import and style token ...
  • eb91679 build(deps): bump the theoretically-non-breaking group across 1 directory wit...
  • See full diff in compare view


Updates @lwc/engine-dom from 6.7.2 to 7.0.1

Release notes

Sourced from @​lwc/engine-dom's releases.

v7.0.1

What's Changed

Full Changelog: https://github.com/salesforce/lwc/compare/v7.0.0...v7.0.1

v7.0.0

LWC v7.0.0 contains breaking changes. Please read carefully below if you are upgrading from v6.

If you are upgrading from v5, please upgrade to v6 first.

[!NOTE] LWC v7 corresponds to Salesforce release Winter '25 (API version 62).

New features

Summary of breaking changes

Breaking changes

[!NOTE] On the Salesforce Lightning platform, this change only applies to components with an API version of 62 or above.

Class object binding is a new feature that makes it more ergonomic to render class attributes in your LWC components. As part of this feature, class rendering has changed for some uncommon use cases.

If you are using a dynamic class in your template:

... (truncated)

Commits


Updates @lwc/engine-server from 6.7.2 to 7.0.1

Release notes

Sourced from @​lwc/engine-server's releases.

v7.0.1

What's Changed

Full Changelog: https://github.com/salesforce/lwc/compare/v7.0.0...v7.0.1

v7.0.0

LWC v7.0.0 contains breaking changes. Please read carefully below if you are upgrading from v6.

If you are upgrading from v5, please upgrade to v6 first.

[!NOTE] LWC v7 corresponds to Salesforce release Winter '25 (API version 62).

New features

Summary of breaking changes

Breaking changes

[!NOTE] On the Salesforce Lightning platform, this change only applies to components with an API version of 62 or above.

Class object binding is a new feature that makes it more ergonomic to render class attributes in your LWC components. As part of this feature, class rendering has changed for some uncommon use cases.

If you are using a dynamic class in your template:

... (truncated)

Commits


Updates @lwc/module-resolver from 6.7.2 to 7.0.1

Release notes

Sourced from @​lwc/module-resolver's releases.

v7.0.1

What's Changed

Full Changelog: https://github.com/salesforce/lwc/compare/v7.0.0...v7.0.1

v7.0.0

LWC v7.0.0 contains breaking changes. Please read carefully below if you are upgrading from v6.

If you are upgrading from v5, please upgrade to v6 first.

[!NOTE] LWC v7 corresponds to Salesforce release Winter '25 (API version 62).

New features

Summary of breaking changes

Breaking changes

[!NOTE] On the Salesforce Lightning platform, this change only applies to components with an API version of 62 or above.

Class object binding is a new feature that makes it more ergonomic to render class attributes in your LWC components. As part of this feature, class rendering has changed for some uncommon use cases.

If you are using a dynamic class in your template:

... (truncated)

Commits


Updates @lwc/synthetic-shadow from 6.7.2 to 7.0.1

Release notes

Sourced from @​lwc/synthetic-shadow's releases.

v7.0.1

What's Changed

Full Changelog: https://github.com/salesforce/lwc/compare/v7.0.0...v7.0.1

v7.0.0

LWC v7.0.0 contains breaking changes. Please read carefully below if you are upgrading from v6.

If you are upgrading from v5, please upgrade to v6 first.

[!NOTE] LWC v7 corresponds to Salesforce release Winter '25 (API version 62).

New features

Summary of breaking changes

Breaking changes

[!NOTE] On the Salesforce Lightning platform, this change only applies to components with an API version of 62 or above.

Class object binding is a new feature that makes it more ergonomic to render class attributes in your LWC components. As part of this feature, class rendering has changed for some uncommon use cases.

If you are using a dynamic class in your template:

... (truncated)

Commits


Updates @lwc/wire-service from 6.7.2 to 7.0.1

Release notes

Sourced from @​lwc/wire-service's releases.

v7.0.1

What's Changed

Full Changelog: https://github.com/salesforce/lwc/compare/v7.0.0...v7.0.1

v7.0.0

LWC v7.0.0 contains breaking changes. Please read carefully below if you are upgrading from v6.

If you are upgrading from v5, please upgrade to v6 first.

[!NOTE] LWC v7 corresponds to Salesforce release Winter '25 (API version 62).

New features

Summary of breaking changes

Breaking changes

[!NOTE] On the Salesforce Lightning platform, this change only applies to components with an API version of 62 or above.

Class object binding is a new feature that makes it more ergonomic to render class attributes in your LWC components. As part of this feature, class rendering has changed for some uncommon use cases.

If you are using a dynamic class in your template:

... (truncated)

Commits


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
dependabot[bot] commented 3 weeks ago

Looks like these dependencies are no longer updatable, so this is no longer needed.