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): update dependency ember-async-data to v1 #740

Open
wants to merge 1 commit into
base: staging
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 5, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
ember-async-data ^0.7.0 -> ^1.0.3 age adoption passing confidence

Release Notes

tracked-tools/ember-async-data (ember-async-data)

v1.0.3

Compare Source

🐛 Bug Fix
📝 Documentation
🏠 Internal
Committers: 2

v1.0.2

Compare Source

🚀 Enhancement
📝 Documentation
🏠 Internal
Committers: 2

v1.0.1

Compare Source

Note: This is a significant bug fix which does (very mildly) break the public API, but necessarily so for the sake of fixing a bug.

🐛 Bug Fix
  • #​578 Bugfix: drop context and stop caching TrackedAsyncData (@​chriskrycho)

    Previously, TrackedAsyncData and the load function accepted a context parameter as their second argument, to use with Ember's destroyables API. However, that was (a) unnecessary and (b) could actually cause memory leaks, literally the opposite of what it was designed to do. To account for this change, simply remove that call from all call sites.

    Additionally, note that this means that you will no longer get a single instance of TrackedAsyncData for the same promise. In most cases, this is irrelevant, and it is likely that removing our cache which attempted to be helpful that way will improve your performance.

Committers: 1

v1.0.0

Compare Source

💥 Breaking Change
🚀 Enhancement
📝 Documentation
🏠 Internal
Committers: 5

v0.7.1: Release 0.7.1

Compare Source

🐛 Bug Fix
Committers: 1

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 added the dependencies Pull requests that update a dependency file label Apr 5, 2023
@Ellen-Wittingen
Copy link
Contributor

We do not use this package anymore, see #751

@renovate renovate bot changed the title chore(deps): update dependency ember-async-data to v1 chore(deps): update dependency ember-async-data to v1 - autoclosed May 6, 2023
@renovate renovate bot closed this May 6, 2023
@renovate renovate bot deleted the renovate/ember-async-data-1.x branch May 6, 2023 16:07
@renovate renovate bot changed the title chore(deps): update dependency ember-async-data to v1 - autoclosed chore(deps): update dependency ember-async-data to v1 May 8, 2023
@renovate renovate bot reopened this May 8, 2023
@renovate renovate bot restored the renovate/ember-async-data-1.x branch May 8, 2023 10:15
@renovate renovate bot force-pushed the renovate/ember-async-data-1.x branch from 8732d88 to 9231d55 Compare May 8, 2023 10:15
@renovate renovate bot force-pushed the renovate/ember-async-data-1.x branch from 9231d55 to 53772ae Compare August 2, 2023 04:21
@renovate renovate bot force-pushed the renovate/ember-async-data-1.x branch from 53772ae to 5589034 Compare October 1, 2023 04:26
@renovate renovate bot force-pushed the renovate/ember-async-data-1.x branch from 5589034 to 7150b4a Compare October 11, 2024 20:56
Copy link
Contributor Author

renovate bot commented Oct 11, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock
/opt/containerbase/tools/corepack/0.29.4/18.14.2/node_modules/corepack/dist/lib/corepack.cjs:22095
  const isURL = URL.canParse(range);
                    ^

TypeError: URL.canParse is not a function
    at parseSpec (/opt/containerbase/tools/corepack/0.29.4/18.14.2/node_modules/corepack/dist/lib/corepack.cjs:22095:21)
    at loadSpec (/opt/containerbase/tools/corepack/0.29.4/18.14.2/node_modules/corepack/dist/lib/corepack.cjs:22158:11)
    at async Engine.findProjectSpec (/opt/containerbase/tools/corepack/0.29.4/18.14.2/node_modules/corepack/dist/lib/corepack.cjs:22348:22)
    at async Engine.executePackageManagerRequest (/opt/containerbase/tools/corepack/0.29.4/18.14.2/node_modules/corepack/dist/lib/corepack.cjs:22404:24)
    at async Object.runMain (/opt/containerbase/tools/corepack/0.29.4/18.14.2/node_modules/corepack/dist/lib/corepack.cjs:23096:5)

Node.js v18.14.2

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant