Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Jun 10, 2023

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
ember-data (source) 3.28.135.8.0 age confidence

Release Notes

warp-drive-data/warp-drive (ember-data)

v5.8.0

Compare Source

v5.7.0

Compare Source

v5.6.0

Compare Source

v5.5.0

Compare Source

v5.4.1

Compare Source

v5.4.0

Compare Source

v5.3.13

Compare Source

v5.3.12

Compare Source

v5.3.11

Compare Source

v5.3.10

Compare Source

v5.3.9

Compare Source

v5.3.8

Compare Source

v5.3.7

Compare Source

v5.3.6

Compare Source

v5.3.5

Compare Source

v5.3.4

Compare Source

🌲 New Deprecation
📝 Documentation
🚀 Enhancement
🐛 Bug Fix
🏠 Internal
Committers: (2)

Chris Thoburn (@​runspired)
@​NullVoxPopuli

For the full project changelog see https://github.com/warp-drive-data/warp-drive/blob/main/CHANGELOG.md

v5.3.3: | I won't lie, it won't be easy

Compare Source

v5.3.3 (2024-03-02)

🐛 Bug Fix
Committers: (1)

Chris Thoburn (@​runspired)

v5.3.2: | Make the music stop before it starts

Compare Source

v5.3.2 (2024-02-29)

🏠 Internal
Committers: (1)

Chris Thoburn (@​runspired)

v5.3.1

Compare Source

🚀 Enhancement
🐛 Bug Fix
🏠 Internal
Committers: (3)

Chris Thoburn (@​runspired)
Eric Kelly (@​HeroicEric)
Krystan HuffMenne (@​gitKrystan)

v5.3.0: | don't forget, baby, I'm a wildcard

Compare Source

The Big Picture

This release primarily focused on polish for the RequestManager story, introducing builder utils, builders for REST ActiveRecord and JSON:API requests as well as serialization utils for JSON:API requests.

As part of shipping serialization utils, we implemented several long-awaited cache features to support them:

  • cache.changedRelationships retrieves a diff of what has been added or removed from each relationship for a resource
  • cache.hasChangedRelationships answers whether any relationships have changed for a resource
  • cache.rollbackRelationships will reset all relationships for that resource to their "remote" state, removing any local changes.

As part of our ongoing efforts to modernize the library and to support the above changes, we implemented several new deprecations.

  • Deprecate legacy import paths (ember-data/) except for ember-data/store
  • Deprecate non-strict-type (e.g. "users" or "myType" instead of "user" and "my-type")
  • Deprecate non-strict-id (e.g . 1 instead of "1")

And in relationships specifically:

  • deprecate fixing non-unique relationship payloads (when the same record is referenced multiple times in a related collection)
  • deprecate remote updates clearing local changes (an upcoming blog post will explain the new behavior here in detail)

Changelog (2023-09-18)

🚀 Enhancement
🐛 Bug Fix
🌲 New Deprecation
🚿 Deprecation Removal
  • adapter, model, private-build-infra, serializer
📝 Documentation
🥅 Test
🏠 Internal
Committers: 11

v5.2.0: | I could've taken you places

Compare Source

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 Fix

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

Compare Source

Changelog (2023-08-17)

🐛 Bug Fix

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

Compare Source

Changelog (2023-07-07)

🐛 Bug Fix
Committers: 1

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

Compare Source

Changelog (2023-06-29)

🐛 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

v5.0.1

Compare Source

v5.0.0: - Rose Colored Lenses

Compare Source

rose-lenses

This release removes code deprecated during 4.x.

🎵 We could stay like this forever.

Changelog

🐛 Bug Fix
🚿 Deprecation Removal
📝 Documentation
Committers: 4

v4.12.8: | Backstreet's Back, Alright!

Compare Source

v4.12.8 (2024-05-08)

🚀 Enhancement
Committers: 1

v4.12.7

Compare Source

v4.12.6

Compare Source

v4.12.5: | Paw Patrol is on a Roll

Compare Source

Changelog (2023-12-04)

🚀 Enhancement
🐛 Bug Fix
Committers: 1

v4.12.4: | Old age is just around the bend

Compare Source

Changelog (2023-10-19)

🐛 Bug Fix
🥅 Test
Committers: 1

v4.12.3: LTS - v4.12.3 | Daydream, déjà vu

Compare Source

Changelog (2023-07-13)

🐛 Bug Fix
Committers: 1

v4.12.2: LTS - v4.12.2 | With our head above the clouds, fallin' stupid like we're kids

Compare Source

Changelog (2023-07-07)

🚀 Enhancement
🐛 Bug Fix
Committers: 1

v4.12.1: LTS - v4.12.1 | Somehow the bedsheets are dirty

Compare Source

Changelog (2023-06-29)

🐛 Bug Fix
Committers: 2

v4.12.0: - Can't Cache This!

Compare Source

MC Hammer Dancing to Can't Touch

It might be the last release of the cycle, but this release comes packed with goodies, so here we'll try to unpack a bit of what's changed.

A Big Step Towards Modern Javascript Build Tooling Support

First, while all addons are still shipping as v1-addons, they now look a lot like v2-addons. We're referring to this as "v1-lite". We pre-build them with rollup leaving only the most minimal babel step to be done when included in your app. Generally this should result in applications seeing improved build times and vastly improved embroider support.

There are still a few blocking issues in ember-auto-import and embroider before EmberData will be able to flip the switch and ship its packages as v2-addons, but that's what is left at this point: a switch to flip. Many thanks to @​richgt for his efforts to help us on this journey.

Documentation

Numerous APIs associated with the Cache, Notifications, Identity Management, and Record Lifecycle have new or improved docs. All packages have had their package overviews updated (some extensively, a few just a bit -- for now), and all packages now have a detailed README.

Deprecation documentation is now written inline alongside the flags that may be used to control granular deprecation stripping. Deprecation documentation will also continue to be added to the deprecation guides, though as of yet the 4.x guides have not been added there (we'd love help with this!).

A major focus of the 5.x cycle will be on refining and polishing the documentation for Polaris. A Quest issue has been opened and we'd love your help!

@​ember-data/request has its first Stable Release!

This package introduces the RequestManager, a package that can be used independently (but also comes bundled with ember-data) that re-envisions how data fetching is managed for both EmberData and applications more broadly.

You may want to peruse the RFC or head over and read its documentation

With this release, all existing request flows in EmberData utilize the RequestManager. While Adapters and Serializers will continue to work via the legacy-handler, these concepts are now entirely optional and users should expect that over the course of the 5.x series as the new request management story is further polished that these legacy concepts will be deprecated and removed from the recommended experience. They will, however, likely live on much longer since their implementation is now as an integration into the request-pipeline of the future and as such is something an application could choose to integrate and continue using.

The Notifications Service has Expanded Capabilities

In addition to subscribing to notifications for individual resources, the notification service now enables subscribing to resource added/removed events and Document added/removed events.

Promises are now Native Promises

EmberData now uses native promises for all promise APIs instead of RSVP Promises. This can have some unexpected timing affects, there's an overview here

The Cache 2.1 Spec is Implemented

What this means in effect is that store.request is now a much ... much more powerful API than store.query. Requests are capable of providing a cache-key or being cached by URL, with full lifecycle control and notification subscriptions. Documents are a first-class citizen of the Cache and EmberData more broadly, we are no longer just a resource-cache. For the full motivations and a discussion of all the various capabilities this unlocks we recommend reading the RFC

To go with this, the JSON:API cache previously provided by @ember-data/record-data is now upgraded to the 2.1 spec and available as the @ember-data/json-api package. While this cache does not yet implement the full suite of cache 2.1 APIs, support for all Cache 2.1 APIs has been added to the store.

Changelog

🚀 Enhancement
🐛 Bug Fix
🚿 Deprecation Removal
📝 Documentation
🥅 Test
🏠 Internal

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/ember-data-5.x branch 2 times, most recently from 958de28 to fd1c659 Compare July 2, 2023 19:34
@renovate renovate bot force-pushed the renovate/ember-data-5.x branch from fd1c659 to 7b6dd68 Compare July 7, 2023 04:02
@renovate renovate bot force-pushed the renovate/ember-data-5.x branch from 7b6dd68 to 1471d0f Compare August 18, 2023 01:24
@renovate renovate bot force-pushed the renovate/ember-data-5.x branch from 1471d0f to 7d3f3fd Compare September 18, 2023 19:56
@renovate renovate bot force-pushed the renovate/ember-data-5.x branch from 7d3f3fd to e7fe65e Compare January 20, 2024 05:12
@renovate renovate bot force-pushed the renovate/ember-data-5.x branch 2 times, most recently from 38aa4f9 to 3fb86e6 Compare February 29, 2024 22:49
@renovate renovate bot force-pushed the renovate/ember-data-5.x branch from 3fb86e6 to b9ccb94 Compare March 2, 2024 06:12
@renovate renovate bot force-pushed the renovate/ember-data-5.x branch 5 times, most recently from d3e5681 to 764a8fc Compare June 21, 2024 20:07
@renovate renovate bot force-pushed the renovate/ember-data-5.x branch from 764a8fc to 4c5dd66 Compare October 22, 2024 01:59
@renovate renovate bot force-pushed the renovate/ember-data-5.x branch from 4c5dd66 to 687d6c0 Compare January 29, 2025 20:26
@renovate renovate bot force-pushed the renovate/ember-data-5.x branch from 687d6c0 to d05c5c4 Compare February 9, 2025 08:25
@renovate renovate bot force-pushed the renovate/ember-data-5.x branch from d05c5c4 to 7439a2d Compare March 20, 2025 23:23
@renovate renovate bot force-pushed the renovate/ember-data-5.x branch 2 times, most recently from 2777483 to 32825a7 Compare April 12, 2025 02:21
@renovate renovate bot force-pushed the renovate/ember-data-5.x branch from 32825a7 to 84ba02c Compare May 9, 2025 07:40
@renovate renovate bot force-pushed the renovate/ember-data-5.x branch from 84ba02c to 5071dbc Compare July 1, 2025 23:49
@renovate renovate bot force-pushed the renovate/ember-data-5.x branch 3 times, most recently from f9eb303 to 25c1f9d Compare August 13, 2025 15:14
@renovate renovate bot force-pushed the renovate/ember-data-5.x branch from 25c1f9d to 87fe03f Compare August 27, 2025 18:27
@renovate renovate bot force-pushed the renovate/ember-data-5.x branch from 87fe03f to 2ac890a Compare September 25, 2025 20:23
@renovate renovate bot force-pushed the renovate/ember-data-5.x branch from 2ac890a to 43f6cf2 Compare October 20, 2025 16:36
@renovate renovate bot force-pushed the renovate/ember-data-5.x branch from 43f6cf2 to 001b499 Compare November 19, 2025 01:00
@renovate renovate bot force-pushed the renovate/ember-data-5.x branch from 001b499 to 08c12c1 Compare December 3, 2025 17:27
@renovate renovate bot force-pushed the renovate/ember-data-5.x branch from 08c12c1 to e54d192 Compare December 31, 2025 13:45
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.

1 participant