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-intl from 3.5.0 to 5.3.1 in /frontend #1395

Closed dependabot-preview[bot] closed 4 years ago

dependabot-preview[bot] commented 4 years ago

Bumps ember-intl from 3.5.0 to 5.3.1.

Release notes

Sourced from ember-intl's releases.

v5.2.0

Notable Changes

  • current locale entangles correctly with autotracking (Thanks to @richard-viney)

v5.0.0

Notable Changes

  • Polyfills have been removed entirely and with it the need to bundle the pluralization rules as they now come from the native Intl.PluralRules API
  • Intl.MessageFormat parser and compiler updated which changes how text and tags are escaped

Breaking Changes

  • Node 8 support dropped
  • Intl.RelativeTime polyfill has been replaced with the native API which behaves entirely different than the previous older spec implementation. Read more in the Migration Document
  • Escaping text has changed and HTML tags now need to be escaped. Read how in the Migration Document
  • Removes shortNumber formatting in favor of newly added native implementation using the "notation": "compact" parameter for Intl.NumberFormat i.e.,
this.intl.formatNumber(1000, {
  notation: "compact" ,
  compactDisplay: "short"
}); // -> 1k

Potentially introduces a breaking change (indirectly)

In this release, we removed an ember-auto-import global app setting that your application still rely on.

In ember-auto-import@1.4.0 they turned a webpack setting for node off.

At the time, this broke every app using ember-intl (and apps that did not rely on ember-intl). If your app imported any dependency via ember-auto-import that relied on node's global object, your app may have no longer built properly and the build error was/is likely cryptic.

To work around this, ember-intl re-set webpack.node.global which had everyone's builds passing again - this issue went unrecognized by most as ember-intl was patching everyone's app even for dependencies that fell outside of ember-intl. Fast forward to 4.3.1, ember-intl no longer needed that option as we dropped the runtime need for setting it. If you now see the bug, you'll want to patch your own applications now.

Full read with solution and explanation for why this isn't a breaking change from ember-intl's perspective: ember-intl/ember-intl#1232

Upgrading dependencies

This is a house keeping release containing dependency upgrades.

v4.0.0-beta.10

No release notes provided.

v4.0.0-beta.9

No release notes provided.

v4.0.0-beta.8

This release includes #815, which adds compatibility for Ember 3.9 and includes some minor breaking changes for edge-case scenarios.

Commits

Commits
  • ba72730 5.3.1
  • 8f57d86 fix: Schedules DOM lang update after localeChanged is dispatched
  • 8ec2cae 5.3.0
  • f0a4898 chore(doc): Rename addon config to configuration
  • 3f5e897 chore(doc): Move addon-config to guides.
  • 4d1042d chore(docs): Adds all build options to new addon config section of docs. (#1364)
  • 150fbea Merge tag 'v5.2.2' of github.com:jasonmit/ember-intl
  • 1f96f57 5.2.2
  • 16ef824 fix: Symbol to String for IE 11 compat. (#1359)
  • d65a1b2 chore: Update README.md (#1360)
  • Additional commits viewable in compare view


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 4 years ago

Superseded by #1406.