search

roschaefer / rundfunk-mitbestimmen

How should your broadcasting fees be spent? Publish your support and improve the program.
https://rundfunk-mitbestimmen.de/
MIT License
39 stars 30 forks source link

Bump ember-concurrency from 0.8.26 to 2.0.2 in /frontend #1464

Closed dependabot-preview[bot] closed 3 years ago

dependabot-preview[bot] commented 3 years ago

Bumps ember-concurrency from 0.8.26 to 2.0.2.

Release notes

Sourced from ember-concurrency's releases.

2.0.2

Bugfixes

  • Ensure lastRunning resets one-by-one as tasks are completed, successfully or not. (Fixes #403)
  • Expose lastValue decorator in TS definitions (Fixes #404)

2.0.1

Bugfixes

  • Prevent synchronous errors in cancelable promise helpers from being rethrown asynchronously later (#402, fixes #400. thanks @Turbo87 for flagging!)
  • Restore access to host context from encapsulated tasks (#401)

2.0.0

ember-concurrency 2.0 is primarily an "engine" replacement. Internally, its been substantially rewritten and decoupled from Ember at it's core. This will enable a much more maintainable codebase, as well as setting the stage for potential extraction of core primatives for us in the broader JavaScript ecosystem.

The application developer-facing changes are fairly minimal, and there are few potentially breaking semantic changes to the operation of the addon.

Please review the 2.0 Upgrade Guide for a thorough description of the changes for app and addon users alike.

New Features

  • Use @tracked underneath on Ember 3.16+ (#354)

    Note: Within applications with both tracked & computed properties, if using a native getter to access task state, and wishing to use it alongside a computed property, @dependantKeyCompat will need to be used on the getter as expected with any other tracked-prop using getter.

  • Implement decorators from ember-concurrency-decorators. The "nice" decorators from ember-concurrency-decorators are now built-in to ember-concurrency, without requiring an additional addon or seperate import. All decorators are available for import directly from the top-level ember-concurrency package.

    Addon maintainers: Please see notes in UPGRADING-2.x.md if you're using decorators currently, and wish to support both ember-concurrency 1.x and 2.x at runtime.

Enhancements

  • Migrate task lifetimes to @ember/destroyable underneath, rather than patching willDestroy (#377).

    Potentially breaking: this drops support for Node 8 and Ember < 3.8 LTS

  • [docs] Rewrite documentation to use native classes and decorators, and update tutorial to show rewriting of async function code, rather than Promise code, as is more common today.

  • Make Task#cancelAll and TaskInstance#cancel awaitable (#396). See topic in UPGRADING-2.x.md for more info.

Removals

  • Remove ability to directly use tasks with {{action}} helper stuff (deprecated in 1.3.0) (#374)
  • Remove get and set compatibility methods from Task, TaskGroup, and TaskInstance.

... (truncated)

Changelog

Sourced from ember-concurrency's changelog.

2.0.2

  • Ensure lastRunning resets one-by-one as tasks are completed, successfully or not. (Fixes #403)
  • Expose lastValue decorator in TS definitions (Fixes #406)

2.0.1

  • Prevent synchronous errors in cancelable promise helpers from being rethrown asynchronously later (#402, fixes #400. thanks @Turbo87 for flagging!)
  • Restore access to host context from encapsulated tasks (#401)

2.0.0

  • No substantive changes from 2.0.0-rc.2

2.0.0-rc.2

  • Make Task#cancelAll and TaskInstance#cancel awaitable (#396). See topic in UPGRADING-2.x.md for more info.
  • Fix TaskProperty extension methods not working with built-in decorators (e.g. ember-concurrency-retryable, ember-concurrency-test-waiters, etc.)
  • [dev] Add test for interop w/ ember-concurrency-decorators
  • [dev] Migrate CI to GitHub Actions (#393)

2.0.0-rc.1

  • Implement decorators from ember-concurrency-decorators. The "nice" decorators from ember-concurrency-decorators are now built-in to ember-concurrency, without requiring an additional addon or seperate import. All decorators are available for import directly from the top-level ember-concurrency package.

    Addon maintainers: Please see notes in UPGRADING-2.x.md if you're using decorators currently, and wish to support both ember-concurrency 1.x and 2.x at runtime.

  • [docs] Rewrite documentation to use native classes and decorators, and update tutorial to show rewriting of async function code, rather than Promise code, as is more common today.

2.0.0-beta.2

  • Migrate task lifetimes to @ember/destroyable underneath, rather than patching willDestroy (#377).

    Potentially breaking: this drops support for Node 8 and Ember < 3.8 LTS

  • Ensure encapsulated task state can be accessed on the TaskInstance (#381, #383)

    Note: this uses Proxy and WeakMap, which may need to be polyfilled on IE 11.

  • Make sure task/group-level state field is tracked (#382)

  • Drop unused broccoli-file-creator and ember-maybe-import-regenerator dependencies.

    Note on ember-maybe-import-regenerator: This was originally added back when generator support in browsers was far lower and Babel 5 and 6 were used. The addon does nothing for Babel 7, which is used for ember-concurrency these

... (truncated)

Commits
  • 9b04e7d Release 2.0.2
  • 531eb8e Add CHANGELOG entry for 2.0.2
  • f412d17 Merge pull request #406 from machty/mf-last_value_ts
  • c7fff62 Expose lastValue decorator in TS definitions
  • bbfab60 Merge pull request #405 from machty/mf-fix_lastRunning
  • 8cd4c19 .lastRunning resets one-by-one as tasks are completed, successfully or not
  • 4718649 Release 2.0.1
  • 67009a2 Add changelog entry for 2.0.1
  • 35a188c Merge pull request #402 from machty/mf-fix_cancelable_promise_eh
  • 4d0c609 Remove unused RawValue stuff
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by m4xm4n, a new releaser for ember-concurrency since your current version.


Dependabot compatibility score

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 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 use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)
dependabot-preview[bot] commented 3 years ago

Superseded by #1470.