Bump @ember-data/tracking from 4.11.3 to 5.2.0

[dependabot[bot]]

Bumps @ember-data/tracking from 4.11.3 to 5.2.0.

Release notes

Sourced from @​ember-data/tracking's releases.

v5.2.0 | I could've taken you places

Changelog (2023-08-17)

• Re-release of 5.1.2 to keep lockstep pace. This release contains no new work.

5.1.2 Contained the following changes

:bug: Bug Fix

• #8750 Backport into release (@​jrjohnson)
  • fix: @​ember-data/debug should declare its peer-dependency on @​ember-data/store #8703
  • fix: de-dupe coalescing when includes or adapterOptions is present but still use findRecord #8704
  • fix: make implicit relationship teardown following delete of related record safe #8705
  • fix: catch errors during didCommit in DEBUG #8708

v5.1.2 | Now I've had time to think it over

Changelog (2023-08-17)

:bug: Bug Fix

• #8750 Backport into release (@​jrjohnson)
  • fix: @​ember-data/debug should declare its peer-dependency on @​ember-data/store #8703
  • fix: de-dupe coalescing when includes or adapterOptions is present but still use findRecord #8704
  • fix: make implicit relationship teardown following delete of related record safe #8705
  • fix: catch errors during didCommit in DEBUG #8708

v5.1.1 - I know it was wrong, but never said I was sorry

Changelog (2023-07-07)

:bug: Bug Fix

• #8685 fix: unloadAll(void) should not destroy the notification manager (backports #8684) (@​runspired)

Committers: 1

• Chris Thoburn (@​runspired)

v5.1.0 - We went to Hell, but we never came back

Changelog (2023-06-29)

:bug: Bug Fix

• #8657 fix: ensure deprecation configs are threaded to each package (@​runspired)
• #8649 fix: NotificationManager should only invoke resource/document callbacks owned by the originating store (@​runspired)

Committers: 1

• Chris Thoburn (@​runspired)

v5.0.0 - Rose Colored Lenses

This release removes code deprecated during 4.x.

... (truncated)

Changelog

Sourced from @​ember-data/tracking's changelog.

5.2.0 (2023-08-17)

• Re-release of 5.1.2 to keep lockstep pace. This release contains no new work.

5.1.2 (2023-08-17)

:bug: Bug Fix

• #8750 Backport into release (@​jrjohnson)
  • fix: @​ember-data/debug should declare its peer-dependency on @​ember-data/store #8703
  • fix: de-dupe coalescing when includes or adapterOptions is present but still use findRecord #8704
  • fix: make implicit relationship teardown following delete of related record safe #8705
  • fix: catch errors during didCommit in DEBUG #8708

5.1.1 (2023-07-07)

:bug: Bug Fix

• #8685 fix: unloadAll(void) should not destroy the notification manager (backports #8684) (@​runspired)

Committers: 1

• Chris Thoburn (@​runspired)

5.1.0 (2023-06-29)

:bug: Bug Fix

• #8657 fix: ensure deprecation configs are threaded to each package (@​runspired)
• #8649 fix: NotificationManager should only invoke resource/document callbacks owned by the originating store (@​runspired)

Committers: 1

• Chris Thoburn (@​runspired)

5.0.1 (2023-06-29)

:bug: Bug Fix

• #8649 fix: NotificationManager should only invoke resource/document callbacks owned by the originating store (@​runspired)

Committers: 1

• Chris Thoburn (@​runspired)

5.0.0 (2023-06-10)

:bug: Bug Fix

• adapter
  • #8621 fix: normalizeErrorResponse should be resilient to non-string details (@​NullVoxPopuli)
• Other
  • #8598 fix: docs generation should maintain a stable relative path (@​runspired)
• json-api, legacy-compat, store
  • #8566 Avoid unnecessary identity notification when record is saved (@​robbytx)
• model
  • #8597 fix: dont share promise cache for all fields (@​runspired)
• store
  • #8594 fix: restore Store extends EmberObject :( (@​runspired)

... (truncated)

Commits

• 92f5f66 Release v5.2.0
• 63ec1b2 Release v5.1.2
• 628fa59 Release v5.1.1
• c7b2f24 Release v5.1.0
• c125234 Release v5.1.0-beta.1
• 49c3ab8 chore(deps): update dependency rollup to ^3.25.3 (#8658)
• 5b76087 chore(deps): update dependency rollup to ^3.25.2 (#8639)
• 4cb73b2 Release v5.2.0-alpha.5
• b1c8aad Release v5.2.0-alpha.4
• bf4fe6d Release v5.2.0-alpha.3
• Additional commits viewable in compare view

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 this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.