Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps-dev): bump ember-data from 5.3.0 to 5.3.8 #966

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 25, 2024

Bumps ember-data from 5.3.0 to 5.3.8.

Release notes

Sourced from ember-data's releases.

v5.3.4 | In a cloud of sparkling dust

image

Yes, this is a patch release packed with goodies. We expect this to be the last patch release of the 5.3 cycle. This puts the release of 5.4 with the first stable releases of @warp-drive/schema-record and @warp-drive/ember ~4 weeks away. Who needs August when you have July?

In no particular order, goodies contained

  • 5.3.4 ships fully as v2-addons
  • all packages ship types, types must be opted into, see the typescript guide
  • native types packages are now available for 5.3
  • mirror packages are now available for 5.3
  • a new cli tool has been added. So far its only niftiness is this cli tool will let you quickly configure your 4.x project for typescript. npx warp-drive retrofit types@canary. Mileage may vary, this works best with 4.12
  • ember-inflector and @​ember/string are no longer project dependencies

Three new deprecations

  • deprecates Store extending EmberObject
  • deprecates using emberData in options in ember-cli-build in favor of setConfig
  • deprecates using ember-inflector for singularization/pluralization support in favor of @ember-data/request-utils (ember-inflector is not deprecated, only WarpDrive/EmberData's consumption of it)

v5.3.4 (2024-06-15)

🌲 New Deprecation

📝 Documentation

🚀 Enhancement

... (truncated)

Changelog

Sourced from ember-data's changelog.

v5.3.8 (2024-06-21)

Committers: (0)

v5.3.4 (2024-06-15)

🌲 New Deprecation

📝 Documentation

🚀 Enhancement

... (truncated)

Commits
  • b819015 Release v5.3.8
  • 8104e27 Release v5.4.0-beta.11
  • 3ec0359 Release v5.4.0-alpha.91
  • 4ad5c74 fix: attempt traversal to find project (#9500)
  • bf1f992 Release v5.4.0-alpha.90
  • 5a700c9 Release v5.4.0-alpha.89
  • 9b12c4e fix: setup deprecation support as early as possible, restore inspector suppor...
  • 16f9992 Use vite's built-in package.json loading to inline names and versions (#9494)
  • bb49391 Release v5.4.0-alpha.88
  • c809f9f Release v5.4.0-alpha.87
  • Additional commits viewable in compare view

Dependabot compatibility score

You can trigger a rebase of this PR 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 <dependency name> 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Jun 25, 2024
Bumps [ember-data](https://github.com/emberjs/data/tree/HEAD/packages/-ember-data) from 5.3.0 to 5.3.8.
- [Release notes](https://github.com/emberjs/data/releases)
- [Changelog](https://github.com/emberjs/data/blob/v5.3.8/CHANGELOG.md)
- [Commits](https://github.com/emberjs/data/commits/v5.3.8/packages/-ember-data)

---
updated-dependencies:
- dependency-name: ember-data
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/ember-data-5.3.8 branch from db0f1fa to 4eda9ca Compare June 28, 2024 12:43
@anehx
Copy link
Member

anehx commented Jun 28, 2024

@dependabot rebase

Copy link
Contributor Author

dependabot bot commented on behalf of github Jun 28, 2024

Looks like this PR is already up-to-date with main! If you'd still like to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

@anehx
Copy link
Member

anehx commented Jul 26, 2024

@dependabot recreate

Copy link
Contributor Author

dependabot bot commented on behalf of github Jul 26, 2024

Looks like ember-data is up-to-date now, so this is no longer needed.

@dependabot dependabot bot closed this Jul 26, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/ember-data-5.3.8 branch July 26, 2024 12:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant