chore(deps): update all dependencies (major) #12389
Open
+113
−129
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
Demo starting at https://ubuntu-com-12389.demos.haus |
renovate
bot
force-pushed
the
renovate/major-all
branch
9 times, most recently
from
96b79e6 to
53b1c11
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
13 times, most recently
from
6b0341a to
5dc1c56
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
3 times, most recently
from
3164e7c to
7637395
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/major-all
branch
3 times, most recently
from
cae4361 to
4bf55b8
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/major-all
branch
from
24ed1e9 to
734f25c
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
734f25c to
fc6eb76
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/major-all
branch
3 times, most recently
from
208e14d to
9e33cc8
Compare
|
@abhigyanghosh30 I see you are assigned to this, do you have any plans to work? |
|
Hey @petesfrench, this is actually blocked because the current version of This will be unblocked once this PR is merged. If you're planning on picking it up then please go ahead. You should assign yourself WD-13248 and WD-14534 as well. Thanks! |
|
@petesfrench No. Maybe next cycle. It has waited so long anyways 😂😂 |
renovate
bot
force-pushed
the
renovate/major-all
branch
from
9e33cc8 to
2f5db88
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/major-all
branch
7 times, most recently
from
066a362 to
99042d7
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
2 times, most recently
from
5e221d2 to
bf31dbc
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
2 times, most recently
from
a846555 to
a4eab38
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
2 times, most recently
from
b25cc7c to
83fb934
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
83fb934 to
787a88c
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
787a88c to
c364f2d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.7.3->3.1.14.1.0->5.5.0^18.3.0->^19.0.0^18.3.0->^19.0.0v4->v58.2.0->9.1.23.6.0->4.1.09.1.0->10.0.124.3.5->25.2.13.1.2->10.0.1==0.8.4->==3.1.020->23==1.24.4->==2.2.1==2022.7.1->==2024.2^18.3.0->^19.0.0^18.3.0->^19.0.0^6.24.1->^7.0.0v43->v4522.04->24.04jammy->noblejammy->nobleRelease Notes
stripe/react-stripe-js (@stripe/react-stripe-js)
v3.1.1Compare Source
Fixes
v3.1.0Compare Source
New features
Changed
v3.0.0Compare Source
New features
Fixes
Changed
v2.9.0Compare Source
New features
v2.8.1Compare Source
Fixes
v2.8.0Compare Source
New features
Fixes
Changed
stripe/stripe-js (@stripe/stripe-js)
v5.5.0Compare Source
New features
v5.4.0Compare Source
New features
Fixes
Changed
v5.3.0Compare Source
Fixes
Changed
v5.2.0Compare Source
New features
Fixes
Changed
v5.1.0Compare Source
New features
Fixes
Changed
v5.0.0Compare Source
New features
Fixes
Changed
v4.10.0Compare Source
New features
Fixes
Changed
v4.9.0Compare Source
New features
Fixes
Changed
v4.8.0Compare Source
New features
v4.7.0Compare Source
New features
Fixes
v4.6.0Compare Source
Fixes
v4.5.0Compare Source
<- Please group the following commits into one of the sections below. -->
<- Remove empty sections when done. -->
New features
Changed
v4.4.0Compare Source
New features
Fixes
Changed
v4.3.0Compare Source
New features
Fixes
Changed
v4.2.0Compare Source
New features
Fixes
Changed
codecov/codecov-action (codecov/codecov-action)
v5Compare Source
What's Changed
${{ inputs.token }}inaction.ymlby @jwodder in https://github.com/codecov/codecov-action/pull/1721Full Changelog: https://github.com/codecov/codecov-action/compare/v5.1.1..v5.1.2
open-cli-tools/concurrently (concurrently)
v9.1.2Compare Source
What's Changed
New Contributors
Full Changelog: open-cli-tools/concurrently@v9.1.1...v9.1.2
v9.1.1Compare Source
What's Changed
Full Changelog: open-cli-tools/concurrently@v9.1.0...v9.1.1
v9.1.0Compare Source
What's Changed
New Contributors
Full Changelog: open-cli-tools/concurrently@v9.0.1...v9.1.0
v9.0.1Compare Source
What's Changed
Full Changelog: open-cli-tools/concurrently@v9.0.0...v9.0.1
v9.0.0Compare Source
v8.2.2Compare Source
What's Changed
New Contributors
Full Changelog: open-cli-tools/concurrently@v8.2.1...v8.2.2
v8.2.1Compare Source
What's Changed
New Contributors
Full Changelog: open-cli-tools/concurrently@v8.2.0...v8.2.1
date-fns/date-fns (date-fns)
v4.1.0Compare Source
This release adds time zone support to format functions (that I somehow missed when working on the feature) and fixes a few bugs.
Make sure also upgrade
TZDateto v1.0.2 as it includes a bunch of critical bug fixes.Fixed
constructFromthrowing an exception onnullarguments. Whilenullisn't allowed, the functions should rather returnInvalid DateorNaNin such cases. See #3885.Added
format,formatISO,formatISO9075,formatRelativeandformatRFC3339. See #3886.v4.0.0Compare Source
I have great news! First, ten years after its release, date-fns finally gets first-class time zone support.
Another great news is that there aren't many breaking changes in this release. All of them are type-related and will affect only those explicitly using internal date-fns types. Finally, it has been less than a year since the last major release, which is an improvement over the previous four years between v2 and v3. I plan on keeping the pace and minimizing breaking changes moving forward.
Read more about the release in the announcement blog post.
- Sasha @kossnocorp
Added
Added time zones support via
@date-fns/tz'sTZDateclass andtzhelper function. See its README for the details about the API.All relevant functions now accept the context
inoption, which allows to specify the time zone to make the calculations in. If the function also returns a date, it will be in the specified time zone:In the example,
addDayswill get the current date and time in Singapore and add 5 days to it.startOfDaywill inherit the date type and return the start of the day in Singapore.Changed
The function arguments, as well as
Interval'sstartandend, now can be of different types, allowing you to mixUTCDate,TZDate,Date, and other extensions, as well as primitives (strings and numbers).The functions will normalize these values, make calculations, and return the result in the same type, preventing any bugs caused by the discrepancy. If passed, the type will be inferred from the context
inoption or the first encountered argument object type. TheInterval'sstartandendwill be considered separately, starting fromstart.In the given example, the result will be in the
TZDateas the first argument is a number, and thestarttakes precedence over theend.BREAKING: This release contains a bunch of types changes that should not affect the library's expected usage. The changes are primarily internal and nuanced, so rather than listing them here, I recommend you running the type checker after the upgrade. If there are unfixable problems, please open an issue.
BREAKING: The package now is ESM-first. The CommonJS is still support and It should not affect most users, but it might break in certains environments. If you encounter any issues, please report them.
Fixed
$by properly wrapping the code in an IIFE.prettier/eslint-config-prettier (eslint-config-prettier)
v10.0.1Compare Source
eslint-config-prettier
10.0.0
Major Changes
5be64beThanks @abrahamguo! - add support for @stylistic formatting rulesVersions before 10.0.0
Version 9.1.0 (2023-12-02)
ESLINT_CONFIG_PRETTIER_NO_DEPRECATEDenvironment variable.Version 9.0.0 (2023-08-05)
"unicode-bom": "off"to your config to disable it again, or run ESLint with--fixto fix all files according to the rule (add or remove BOM). Thanks to Nicolas Stepien (@nstepien)!Version 8.10.0 (2023-08-03)
Version 8.9.0 (2023-07-27)
Version 8.8.0 (2023-03-20)
Version 8.7.0 (2023-03-06)
Version 8.6.0 (2023-01-02)
Version 8.5.0 (2022-03-02)
Version 8.4.0 (2022-02-19)
Version 8.3.0 (2021-04-24)
Version 8.2.0 (2021-04-13)
Version 8.1.0 (2021-02-24)
Version 8.0.0 (2021-02-21)
Changed: All configs have been merged into one!
To upgrade, change:
{ "extends": [ "some-other-config-you-use", "prettier", "prettier/@​typescript-eslint", "prettier/babel", "prettier/flowtype", "prettier/react", "prettier/standard", "prettier/unicorn", "prettier/vue" ] }Into:
{ "extends": [ "some-other-config-you-use", "prettier" ] }The
"prettier"config now includes not just ESLint core rules, but also rules from all plugins. Much simpler!So … what’s the catch? Why haven’t we done this earlier? Turns out it’s just a sad mistake. I (@lydell) was confused when testing, and thought that turning off unknown rules in a config was an error. Thanks to Georgii Dolzhykov (@thorn0) for pointing this out!
If you use [eslint-plugin-prettier], all you need is [plugin:prettier/recommended]:
{ "extends": [ "some-other-config-you-use", "plugin:prettier/recommended" ] }(The ["prettier/prettier" config][prettier-prettier-config] still exists separately. It’s the odd one out. The main
"prettier"config does not include the rules from it.)Changed: The CLI helper tool now only prints warnings for [arrow-body-style] and [prefer-arrow-callback], just like other “special rules.” This means that if you’ve decided to use those rules and [eslint-plugin-prettier] at the same time, you’ll get warnings but exit code zero (success).
Version 7.2.0 (2021-01-18)
Version 7.1.0 (2020-12-19)
Version 7.0.0 (2020-12-05)
Changed: At least ESLint 7.0.0 is now required.
Changed: [arrow-body-style] and [prefer-arrow-callback] are no longer turned off by default. They only need to be turned off if you use [eslint-plugin-prettier]. If you do, add
"prettier/prettier"to your"extends"array to turn them off again.{ "extends": ["prettier", "prettier/prettier"], "plugins": ["prettier"], "rules": { "prettier/prettier": "error" } }Alternatively, update [eslint-plugin-prettier] to version 3.2.0 or later which automatically turns off these two rules in its
"plugin:prettier/recommended"config.The CLI helper tool only warns about these rules if you have the
"prettier/prettier"rule enabled for a file.Changed:
no-tabsis now a validatable rule. If you use it, you should enableallowIndentationTabsso that the rule works regardless of your Prettier config:{ "rules": { "no-tabs": ["error", { "allowIndentationTabs": true }] } }Changed: The CLI helper tool is now called just
eslint-config-prettierinstead ofeslint-config-prettier-check. This is so thatnpx eslint-config-prettieralways works regardless of whether you have already installedeslint-config-prettieror not: If you have, the local installation is used; if you haven’t,npxdownloads a temporary copy.Changed: The CLI helper tool no longer requires you to pipe the output of
eslint --print-configto it. Instead, it does that automatically for you via ESLint API:s added in ESLint v7.Before:
After:
Improved: The npm package is now 75% smaller.
Version 6.15.0 (2020-10-27)
Version 6.14.0 (2020-10-21)
Version 6.13.0 (2020-10-16)
Version 6.12.0 (2020-09-25)
Version 6.11.0 (2020-04-21)
Version 6.10.1 (2020-03-22)
npxwhen running the CLI helper tool.Version 6.10.0 (2020-01-28)
Version 6.9.0 (2019-12-27)
Version 6.8.0 (2019-12-25)
Version 6.7.0 (2019-11-19)
Version 6.6.0 (2019-11-17)
Version 6.5.0 (2019-10-26)
Version 6.4.0 (2019-10-05)
Version 6.3.0 (2019-09-10)
Version 6.2.0 (2019-09-03)
Version 6.1.0 (2019-08-19)
Version 6.0.0 (2019-06-25)
Changed: The CLI helper tool now considers [no-confusing-arrow] to conflict if you use the default value of its
allowParensoption. The default was changed totruein ESLint 6, which conflicts with Prettier.If the CLI helper tool gives you errors about this after upgrading, the solution is to change this:
{ "rules": { "no-confusing-arrow": ["error"] } }Into this:
{ "rules": { "no-confusing-arrow": ["error", { "allowParens": false }] } }The latter works in both ESLint 6 as well as in ESLint 5 and older.
Improved:
eslint --print-configusage instructions. The CLI tool help text as well as the documentation has been updated to suggest commands that work in ESLint 6.0 as well as in ESLint 5 and older. (Instead ofeslint --print-config ., useeslint --print-config path/to/main.js.)Version 5.1.0 (2019-06-25)
Version 5.0.0 (2019-06-15)
Removed: [react/self-closing-comp]. This rule was added in v4.1.0 not because it conflicted with Prettier but because it was unnecessary when using Prettier. However, in v1.18.0 [Prettier stopped converting empty elements to self-closing elements][prettier-self-closing]. So the rule is not unnecessary anymore.
If you use Prettier v1.17.1 or older you should be able to upgrade eslint-config-prettier to v5.0.0 without having to do anything else.
If you use Prettier v1.18.0 or newer, you might get lint errors about for example changing
<div></div>into<div />. You have two options:eslint --fixif you prefer to enforce self-closing elements where possible. This should fix all the errors."react/self-closing-comp": "off"to your ESLint config if you use autofix from your editor and you face the same [issue as Prettier did][prettier-self-closing].Changed: Node.js 6 is no longer officially supported, but v5.0.0 should still work with it.
Version 4.3.0 (2019-05-16)
Version 4.2.0 (2019-04-25)
Version 4.1.0 (2019-02-26)
Version 4.0.0 (2019-01-26)
--fix. They are turned off by default, and the CLI helper tool will warn about them (but not error if you do enable them). This won’t break your linting checks, but do note that these rules will be disabled unless you explicitly enable them again, and that you might see new warnings when running the CLI helper tool.Version 3.6.0 (2019-01-19)
Version 3.5.0 (2019-01-16)
vue/no-layout-ruleslist, since there can be layout rules that don’t conflict with but rather complement Prettier.Version 3.4.0 (2019-01-13)
vue/no-layout-rulesconfig behind the scenes, so it should automatically stay up-to-date when new eslint-plugin-vue versions are released. Thanks to Michał Sajnóg (@michalsnik)!Version 3.3.0 (2018-11-11)
Version 3.2.0 (2018-11-10)
Version 3.1.0 (2018-09-22)
Version 3.0.1 (2018-08-13)
eslint --print-configusage instructions.Version 3.0.0 (2018-08-13)
Version 2.10.0 (2018-08-13)
Version 2.9.0 (2017-11-26)
Version 2.8.0 (2017-11-19)
Version 2.7.0 (2017-11-01)
Configuration
📅 Schedule: Branch creation - "on the first day of january" (UTC), 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.