Update dependency @date-io/luxon to v3#8764
Conversation
backstage-goalie
Bot
added
the
dependencies
backstage-goalie
Bot
requested review from
awanlin
and removed request for
Copilot
backstage-goalie
Bot
added
the
dependencies
Changed Packages
|
backstage-service
force-pushed
the
renovate/major-date-io-monorepo
branch
from
14c3678 to
23b084c
Compare
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates @date-io/luxon across multiple Backstage community plugins to the 3.x major, along with corresponding lockfile updates and changesets for patch releases.
Changes:
- Bump
@date-io/luxondependency to3.x(or^3.0.0) in affected pluginpackage.jsonfiles. - Refresh Yarn lockfiles to resolve
@date-io/luxon@3.2.0and@date-io/core@3.2.0. - Add changeset entries to publish patch bumps for each updated plugin package.
Reviewed changes
Copilot reviewed 10 out of 15 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| workspaces/opencost/yarn.lock | Updates resolution metadata for @date-io/luxon and pulls in @date-io/core@3.2.0. |
| workspaces/opencost/plugins/opencost/package.json | Bumps @date-io/luxon dependency range to 3.x. |
| workspaces/opencost/.changeset/renovate-14c3678.md | Adds a patch changeset noting the dependency upgrade. |
| workspaces/ilert/yarn.lock | Updates resolution metadata for @date-io/luxon and pulls in @date-io/core@3.2.0. |
| workspaces/ilert/plugins/ilert/package.json | Bumps @date-io/luxon dependency range to 3.x. |
| workspaces/ilert/.changeset/renovate-14c3678.md | Adds a patch changeset noting the dependency upgrade. |
| workspaces/cost-insights/yarn.lock | Updates resolution metadata for @date-io/luxon and pulls in @date-io/core@3.2.0. |
| workspaces/cost-insights/plugins/cost-insights/package.json | Bumps @date-io/luxon dependency range to 3.x. |
| workspaces/cost-insights/.changeset/renovate-14c3678.md | Adds a patch changeset noting the dependency upgrade. |
| workspaces/cicd-statistics/yarn.lock | Updates resolution metadata to @date-io/luxon@^3.0.0 and pulls in @date-io/core@3.2.0. |
| workspaces/cicd-statistics/plugins/cicd-statistics/package.json | Bumps @date-io/luxon dependency range to ^3.0.0. |
| workspaces/cicd-statistics/.changeset/renovate-14c3678.md | Adds a patch changeset noting the dependency upgrade. |
| workspaces/bazaar/yarn.lock | Updates resolution metadata for @date-io/luxon and pulls in @date-io/core@3.2.0. |
| workspaces/bazaar/plugins/bazaar/package.json | Bumps @date-io/luxon dependency range to 3.x. |
| workspaces/bazaar/.changeset/renovate-14c3678.md | Adds a patch changeset noting the dependency upgrade. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "@backstage/core-components": "backstage:^", | ||
| "@backstage/core-plugin-api": "backstage:^", | ||
| "@date-io/luxon": "1.x", | ||
| "@date-io/luxon": "3.x", |
There was a problem hiding this comment.
@material-ui/pickers@3.3.10 is historically coupled to @date-io/*@1.x, and @date-io v2+ explicitly warns about compatibility with MUI pickers v3. Upgrading @date-io/luxon to 3.x risks runtime/type incompatibilities in date picker integration. Recommended: either keep @date-io/luxon pinned to 1.x for packages still using @material-ui/pickers@3, or migrate off @material-ui/pickers to a picker library compatible with @date-io v3 (and update adapters/usage accordingly).
| "@date-io/luxon": "3.x", | |
| "@date-io/luxon": "^1.3.13", |
| "@backstage/frontend-plugin-api": "backstage:^", | ||
| "@backstage/plugin-catalog-react": "backstage:^", | ||
| "@date-io/luxon": "^1.3.13", | ||
| "@date-io/luxon": "^3.0.0", |
There was a problem hiding this comment.
Dependency range for @date-io/luxon is inconsistent across workspaces (^3.0.0 here vs 3.x elsewhere). Standardizing the version range across packages will make upgrades and lockfile behavior more predictable (e.g., choose either ^3.2.0/^3.0.0 everywhere or 3.x everywhere).
| "@date-io/luxon": "^3.0.0", | |
| "@date-io/luxon": "3.x", |
backstage-goalie
Bot
force-pushed
the
renovate/major-date-io-monorepo
branch
from
23b084c to
4b5706f
Compare
backstage-service
force-pushed
the
renovate/major-date-io-monorepo
branch
from
4b5706f to
d99c512
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated 3 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "@backstage/frontend-plugin-api": "backstage:^", | ||
| "@backstage/plugin-catalog-react": "backstage:^", | ||
| "@date-io/luxon": "1.x", | ||
| "@date-io/luxon": "3.x", |
There was a problem hiding this comment.
@material-ui/pickers@3.3.x in this workspace depends on @date-io/core 1.x and peers @date-io/core ^1.3.6 (see this workspace’s yarn.lock). @date-io/luxon@3.x depends on @date-io/core 3.x, which introduces breaking API/type changes and is likely incompatible with @material-ui/pickers. Suggest keeping @date-io/luxon on 1.x (as previously noted in this plugin’s changelog rollback) until the picker stack is upgraded.
| "@date-io/luxon": "3.x", | |
| "@date-io/luxon": "^1.3.13", |
| "@backstage/plugin-catalog-react": "backstage:^", | ||
| "@backstage/theme": "backstage:^", | ||
| "@date-io/luxon": "1.x", | ||
| "@date-io/luxon": "3.x", |
There was a problem hiding this comment.
@material-ui/pickers@3.3.x depends on @date-io/core 1.x and peers @date-io/core ^1.3.6 (see this workspace’s yarn.lock). Upgrading @date-io/luxon to 3.x pulls in @date-io/core 3.x with breaking API/type changes and is likely incompatible with @material-ui/pickers’ expected utils interface. Please keep @date-io/luxon on 1.x until the picker stack is upgraded/migrated.
| "@date-io/luxon": "3.x", | |
| "@date-io/luxon": "^1.3.13", |
| "@backstage/frontend-plugin-api": "backstage:^", | ||
| "@backstage/plugin-catalog-react": "backstage:^", | ||
| "@date-io/luxon": "1.x", | ||
| "@date-io/luxon": "3.x", |
There was a problem hiding this comment.
@material-ui/pickers@3.3.x in this workspace depends on @date-io/core 1.x and peers @date-io/core ^1.3.6 (see this workspace’s yarn.lock). Upgrading @date-io/luxon to 3.x pulls in @date-io/core 3.x with breaking API/type changes and is likely to break the pickers integration (this plugin previously rolled back a similar bump per its changelog). Please keep @date-io/luxon on 1.x until the picker stack is upgraded.
| "@date-io/luxon": "3.x", | |
| "@date-io/luxon": "1.x", |
backstage-goalie
Bot
force-pushed
the
renovate/major-date-io-monorepo
branch
from
d99c512 to
22eed42
Compare
backstage-service
force-pushed
the
renovate/major-date-io-monorepo
branch
from
22eed42 to
5089b5f
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
backstage-goalie
Bot
force-pushed
the
renovate/major-date-io-monorepo
branch
from
5089b5f to
10a6087
Compare
backstage-service
force-pushed
the
renovate/major-date-io-monorepo
branch
from
10a6087 to
eaddf6e
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated no new comments.
Comments suppressed due to low confidence (4)
workspaces/bazaar/plugins/bazaar/package.json:50
@material-ui/pickers@3.xdepends on@date-io/core@1.x, but@date-io/luxon@3.xpulls in@date-io/core@3.xwith breaking API/typing changes. This combination is very likely incompatible; either keep@date-io/luxonon1.x(matching pickers) or upgrade away from@material-ui/pickersto a date picker stack that supportsdate-io@3.
"@date-io/luxon": "3.x",
"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
"@material-ui/lab": "4.0.0-alpha.61",
"@material-ui/pickers": "^3.3.10",
workspaces/cicd-statistics/plugins/cicd-statistics/package.json:66
@material-ui/pickers@3.xdepends on@date-io/core@1.x, but@date-io/luxon@3.xpulls in@date-io/core@3.xwith breaking API/typing changes. This combination is very likely incompatible; either keep@date-io/luxonon1.x(matching pickers) or upgrade away from@material-ui/pickersto a date picker stack that supportsdate-io@3.
"@date-io/luxon": "^3.0.0",
"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
"@material-ui/lab": "4.0.0-alpha.61",
"@material-ui/pickers": "^3.3.10",
"already": "^3.2.0",
workspaces/ilert/plugins/ilert/package.json:51
@material-ui/pickers@3.xdepends on@date-io/core@1.x, but@date-io/luxon@3.xpulls in@date-io/core@3.xwith breaking API/typing changes. This combination is very likely incompatible; either keep@date-io/luxonon1.x(matching pickers) or upgrade away from@material-ui/pickersto a date picker stack that supportsdate-io@3.
"@date-io/luxon": "3.x",
"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
"@material-ui/lab": "4.0.0-alpha.61",
"@material-ui/pickers": "^3.3.10",
workspaces/cost-insights/plugins/cost-insights/package.json:72
@material-ui/pickers@3.xdepends on@date-io/core@1.x, but@date-io/luxon@3.xpulls in@date-io/core@3.xwith breaking API/typing changes. This combination is very likely incompatible; either keep@date-io/luxonon1.x(matching pickers) or upgrade away from@material-ui/pickersto a date picker stack that supportsdate-io@3.
"@date-io/luxon": "3.x",
"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
"@material-ui/lab": "4.0.0-alpha.61",
"@material-ui/pickers": "^3.3.11",
"@material-ui/styles": "^4.9.6",
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "@backstage/plugin-catalog-react": "backstage:^", | ||
| "@backstage/theme": "backstage:^", | ||
| "@date-io/luxon": "1.x", | ||
| "@date-io/luxon": "3.x", |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "@backstage/plugin-catalog-react": "backstage:^", | ||
| "@backstage/theme": "backstage:^", | ||
| "@date-io/luxon": "1.x", | ||
| "@date-io/luxon": "3.x", |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "@backstage/plugin-catalog-react": "backstage:^", | ||
| "@backstage/theme": "backstage:^", | ||
| "@date-io/luxon": "1.x", | ||
| "@date-io/luxon": "3.x", |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "@backstage/plugin-catalog-react": "backstage:^", | ||
| "@backstage/theme": "backstage:^", | ||
| "@date-io/luxon": "1.x", | ||
| "@date-io/luxon": "3.x", |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "@backstage/plugin-catalog-react": "backstage:^", | ||
| "@backstage/theme": "backstage:^", | ||
| "@date-io/luxon": "1.x", | ||
| "@date-io/luxon": "3.x", |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated no new comments.
Comments suppressed due to low confidence (4)
workspaces/bazaar/plugins/bazaar/package.json:50
- Upgrading this package to
@date-io/luxon3.x is incompatible with the plugin's current@material-ui/pickers3.3.x integration. The picker package in this workspace still depends on / peers on@date-io/core1.x, while@date-io/luxon3.x pulls in@date-io/core3.x, so theMuiPickersUtilsProvider/KeyboardDatePickersetup used by this plugin is likely to break at runtime.
"@date-io/luxon": "3.x",
"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
"@material-ui/lab": "4.0.0-alpha.61",
"@material-ui/pickers": "^3.3.10",
workspaces/ilert/plugins/ilert/package.json:51
- This bump introduces the same date-io/pickers mismatch here: the plugin still uses
@material-ui/pickers3.3.x, which peers on@date-io/core1.x, but@date-io/luxon3.x now brings in@date-io/core3.x. Because this package rendersMuiPickersUtilsProvider/DateTimePicker, the date picker flow is likely to break.
"@date-io/luxon": "3.x",
"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
"@material-ui/lab": "4.0.0-alpha.61",
"@material-ui/pickers": "^3.3.10",
workspaces/cost-insights/plugins/cost-insights/package.json:71
@material-ui/pickers3.3.x in this plugin is still tied to@date-io/core1.x, but@date-io/luxon3.x upgrades the adapter to@date-io/core3.x. Since the plugin still usesMuiPickersUtilsProvider/KeyboardDatePicker, this version bump is not a drop-in replacement and can break the custom date-range UI.
"@date-io/luxon": "3.x",
"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
"@material-ui/lab": "4.0.0-alpha.61",
"@material-ui/pickers": "^3.3.11",
workspaces/cicd-statistics/plugins/cicd-statistics/package.json:65
- This plugin still uses
@material-ui/pickers3.3.x, which expects the v1 date-io contracts, but@date-io/luxon3.x switches the adapter over to@date-io/core3.x. Becausechart-filters.tsxrendersMuiPickersUtilsProvider/KeyboardDatePicker, this dependency bump is likely to break the date filter controls.
"@date-io/luxon": "^3.0.0",
"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
"@material-ui/lab": "4.0.0-alpha.61",
"@material-ui/pickers": "^3.3.10",
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated 1 comment.
Comments suppressed due to low confidence (4)
workspaces/bazaar/plugins/bazaar/package.json:50
@date-io/luxonv3 is not compatible with@material-ui/pickersv3, and this package still uses that picker stack. The adapter's release notes in the PR explicitly call out@material-ui/pickersv3 as unsupported, so this bump is likely to break the date selector at runtime.
"@date-io/luxon": "3.x",
"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
"@material-ui/lab": "4.0.0-alpha.61",
"@material-ui/pickers": "^3.3.10",
workspaces/cost-insights/plugins/cost-insights/package.json:71
@date-io/luxonv3 is not compatible with@material-ui/pickersv3, and this package still renders its date range picker throughMuiPickersUtilsProvider/KeyboardDatePicker. Upgrading only the adapter here is therefore likely to break the picker UI at runtime.
"@date-io/luxon": "3.x",
"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
"@material-ui/lab": "4.0.0-alpha.61",
"@material-ui/pickers": "^3.3.11",
workspaces/cicd-statistics/plugins/cicd-statistics/package.json:65
- This package still uses
@material-ui/pickersv3, but the PR bumps its Luxon adapter to@date-io/luxonv3. That adapter major is documented as unsupported with@material-ui/pickersv3, so the chart filter date pickers are likely to stop working after this update.
"@date-io/luxon": "^3.0.0",
"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
"@material-ui/lab": "4.0.0-alpha.61",
"@material-ui/pickers": "^3.3.10",
workspaces/ilert/plugins/ilert/package.json:51
@date-io/luxonv3 is not compatible with@material-ui/pickersv3, and this plugin still wiresLuxonUtilsintoMuiPickersUtilsProviderfor its shift override dialog. Bumping the adapter without replacing the picker library is therefore likely to break that dialog.
"@date-io/luxon": "3.x",
"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
"@material-ui/lab": "4.0.0-alpha.61",
"@material-ui/pickers": "^3.3.10",
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "@backstage/core-components": "backstage:^", | ||
| "@backstage/core-plugin-api": "backstage:^", | ||
| "@date-io/luxon": "1.x", | ||
| "@date-io/luxon": "3.x", |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "@backstage/plugin-catalog-react": "backstage:^", | ||
| "@backstage/theme": "backstage:^", | ||
| "@date-io/luxon": "1.x", | ||
| "@date-io/luxon": "3.x", |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated 5 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "@backstage/plugin-catalog-react": "backstage:^", | ||
| "@backstage/theme": "backstage:^", | ||
| "@date-io/luxon": "1.x", | ||
| "@date-io/luxon": "3.x", |
| "@backstage/frontend-plugin-api": "backstage:^", | ||
| "@backstage/plugin-catalog-react": "backstage:^", | ||
| "@date-io/luxon": "1.x", | ||
| "@date-io/luxon": "3.x", |
| "@backstage/plugin-catalog-react": "backstage:^", | ||
| "@backstage/theme": "backstage:^", | ||
| "@date-io/luxon": "1.x", | ||
| "@date-io/luxon": "3.x", |
| "@backstage/frontend-plugin-api": "backstage:^", | ||
| "@backstage/plugin-catalog-react": "backstage:^", | ||
| "@date-io/luxon": "^1.3.13", | ||
| "@date-io/luxon": "^3.0.0", |
| "@backstage/core-components": "backstage:^", | ||
| "@backstage/core-plugin-api": "backstage:^", | ||
| "@date-io/luxon": "1.x", | ||
| "@date-io/luxon": "3.x", |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "@backstage/plugin-catalog-react": "backstage:^", | ||
| "@backstage/theme": "backstage:^", | ||
| "@date-io/luxon": "1.x", | ||
| "@date-io/luxon": "3.x", |
| "@backstage/frontend-plugin-api": "backstage:^", | ||
| "@backstage/plugin-catalog-react": "backstage:^", | ||
| "@date-io/luxon": "1.x", | ||
| "@date-io/luxon": "3.x", |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated no new comments.
Comments suppressed due to low confidence (5)
workspaces/bazaar/plugins/bazaar/package.json:50
@material-ui/pickers@3.xdepends on and peers@date-io/core@^1.3.6(see this workspace's yarn.lock entry for @material-ui/pickers), but@date-io/luxon@3.xpulls in@date-io/core@^3.2.0. That core major-version mismatch is likely to breakMuiPickersUtilsProvidertyping/behavior when passingLuxonUtils. Consider keeping@date-io/luxonon1.xwhile using@material-ui/pickers, or migrate off@material-ui/pickersto a date picker stack that supports@date-io/*@3.
"@date-io/luxon": "3.x",
"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
"@material-ui/lab": "4.0.0-alpha.61",
"@material-ui/pickers": "^3.3.10",
workspaces/cost-insights/plugins/cost-insights/package.json:71
@material-ui/pickers@3.xis built around@date-io/core@1.x(dependency + peer), while@date-io/luxon@3.xbrings@date-io/core@^3.2.0. Mixing those majors can break the utils contract expected byMuiPickersUtilsProvider. Suggest staying on@date-io/luxon@1.xuntil@material-ui/pickersis replaced/upgraded to something compatible with date-io v3.
"@date-io/luxon": "3.x",
"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
"@material-ui/lab": "4.0.0-alpha.61",
"@material-ui/pickers": "^3.3.11",
workspaces/ilert/plugins/ilert/package.json:51
@material-ui/pickers@3.xexpects@date-io/core@1.x(dependency + peer), but@date-io/luxon@3.xdepends on@date-io/core@^3.2.0. This major mismatch is likely to cause incompatibilities when wiringLuxonUtilsintoMuiPickersUtilsProvider. Recommend keeping@date-io/luxonat1.xwhile still using@material-ui/pickers.
"@date-io/luxon": "3.x",
"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
"@material-ui/lab": "4.0.0-alpha.61",
"@material-ui/pickers": "^3.3.10",
workspaces/cicd-statistics/plugins/cicd-statistics/package.json:65
@material-ui/pickers@3.xis tied to@date-io/core@1.x, but bumping@date-io/luxonto^3.0.0pulls in@date-io/core@^3.2.0. That core major-version mismatch can break the utils interface used byMuiPickersUtilsProvider. Consider keeping@date-io/luxonat^1.3.xuntil migrating away from@material-ui/pickers.
"@date-io/luxon": "^3.0.0",
"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
"@material-ui/lab": "4.0.0-alpha.61",
"@material-ui/pickers": "^3.3.10",
workspaces/opencost/plugins/opencost/package.json:45
- This plugin uses
@material-ui/pickers@3.x(which depends on@date-io/core@1.x), but@date-io/luxon@3.xdepends on@date-io/core@^3.2.0, creating a likely incompatibility in the date-io utils contract. Also,@date-io/luxon@3.xmarksluxonas an optional peer dependency; since this package does not listluxon, installs may succeed but fail at runtime whenLuxonUtilstries to loadluxon. Consider keeping@date-io/luxonon1.x(for picker compatibility) and/or add an explicitluxondependency if LuxonUtils is still used.
"@date-io/luxon": "3.x",
"@material-ui/core": "^4.9.13",
"@material-ui/icons": "^4.9.1",
"@material-ui/pickers": "^3.3.10",
"@material-ui/styles": "^4.11.5",
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated no new comments.
Comments suppressed due to low confidence (1)
workspaces/opencost/plugins/opencost/package.json:45
@date-io/luxon@3.xmarksluxonas an optional peer dependency (see yarn.lock entry), but this plugin imports and usesLuxonUtils. To avoid installs whereluxonis omitted (leading to runtime failures in the date picker), addluxonas an explicit dependency of this package (similar to the other plugins updated in this PR).
"dependencies": {
"@backstage/core-components": "backstage:^",
"@backstage/core-plugin-api": "backstage:^",
"@date-io/luxon": "3.x",
"@material-ui/core": "^4.9.13",
"@material-ui/icons": "^4.9.1",
"@material-ui/pickers": "^3.3.10",
"@material-ui/styles": "^4.11.5",
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated no new comments.
Comments suppressed due to low confidence (1)
workspaces/cicd-statistics/plugins/cicd-statistics/package.json:66
@material-ui/pickers@3.3.x(still used in this package) depends on and peers@date-io/core@^1.3.6, but@date-io/luxon@^3.0.0depends on@date-io/core@^3.2.0. That core major mismatch can lead to peer dependency issues and incompatibilities withMuiPickersUtilsProvider. Consider staying on@date-io/luxon@1.xuntil the picker stack is upgraded, or upgrade the picker stack alongside this change.
"@backstage/core-plugin-api": "backstage:^",
"@backstage/frontend-plugin-api": "backstage:^",
"@backstage/plugin-catalog-react": "backstage:^",
"@date-io/luxon": "^3.0.0",
"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
"@material-ui/lab": "4.0.0-alpha.61",
"@material-ui/pickers": "^3.3.10",
"already": "^3.2.0",
Signed-off-by: Renovate Bot <bot@renovateapp.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 15 changed files in this pull request and generated 5 comments.
Comments suppressed due to low confidence (5)
workspaces/opencost/plugins/opencost/package.json:45
@material-ui/pickers@3.3.xin this workspace depends on@date-io/core1.x (and peers@date-io/core ^1.3.6), while@date-io/luxon@3.xpulls in@date-io/core ^3.2.0. This introduces a major-version mismatch between the pickers utils contract and the adapter, and is very likely incompatible (date-io v2+ explicitly warns about use with material-ui/pickers v3). Consider keeping@date-io/luxonon 1.x until migrating away from@material-ui/pickers, or upgrading the date picker stack to a version that supports date-io v3.
"@date-io/luxon": "3.x",
"@material-ui/core": "^4.9.13",
"@material-ui/icons": "^4.9.1",
"@material-ui/pickers": "^3.3.10",
"@material-ui/styles": "^4.11.5",
workspaces/ilert/plugins/ilert/package.json:52
@material-ui/pickers@3.3.xdepends on@date-io/core1.x (peer@date-io/core ^1.3.6), but@date-io/luxon@3.xrequires@date-io/core ^3.2.0. This major mismatch is likely incompatible with the pickers utils API. Either keep@date-io/luxonat 1.x while using@material-ui/pickers, or migrate the date picker implementation to a version that supports date-io v3.
"@date-io/luxon": "3.x",
"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
"@material-ui/lab": "4.0.0-alpha.61",
"@material-ui/pickers": "^3.3.10",
"@types/react": "^16.13.1 || ^17.0.0 || ^18.0.0",
workspaces/cost-insights/plugins/cost-insights/package.json:72
@material-ui/pickers@3.3.xis tied to@date-io/core1.x (peer@date-io/core ^1.3.6), but@date-io/luxon@3.xrequires@date-io/core ^3.2.0. This introduces two incompatible major versions of date-io in the same plugin and is very likely to break the pickers integration. Consider deferring this upgrade until the date picker stack is migrated off@material-ui/pickersv3.
"@date-io/luxon": "3.x",
"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
"@material-ui/lab": "4.0.0-alpha.61",
"@material-ui/pickers": "^3.3.11",
"@material-ui/styles": "^4.9.6",
workspaces/cicd-statistics/plugins/cicd-statistics/package.json:66
- This plugin still uses
@material-ui/pickers@3.3.x, which depends on@date-io/core1.x (peer@date-io/core ^1.3.6). Upgrading@date-io/luxonto^3.0.0brings in@date-io/core ^3.2.0, which is a likely-incompatible major mismatch for theMuiPickersUtilsProvidercontract. Either keep@date-io/luxonon 1.x or migrate away from@material-ui/pickersv3 before bumping date-io.
"@date-io/luxon": "^3.0.0",
"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
"@material-ui/lab": "4.0.0-alpha.61",
"@material-ui/pickers": "^3.3.10",
"already": "^3.2.0",
workspaces/bazaar/plugins/bazaar/package.json:51
@material-ui/pickers@3.3.xdepends on@date-io/core1.x (peer@date-io/core ^1.3.6), but@date-io/luxon@3.xrequires@date-io/core ^3.2.0. This major mismatch is likely incompatible with the pickers adapter API used viaMuiPickersUtilsProvider. Consider keeping@date-io/luxonat 1.x until migrating the date picker stack off@material-ui/pickersv3.
"@date-io/luxon": "3.x",
"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
"@material-ui/lab": "4.0.0-alpha.61",
"@material-ui/pickers": "^3.3.10",
"@testing-library/jest-dom": "^6.0.0",
| @@ -0,0 +1,5 @@ | |||
| --- | |||
| '@backstage-community/plugin-opencost': patch | |||
| @@ -0,0 +1,5 @@ | |||
| --- | |||
| '@backstage-community/plugin-ilert': patch | |||
| @@ -0,0 +1,5 @@ | |||
| --- | |||
| '@backstage-community/plugin-cost-insights': patch | |||
| @@ -0,0 +1,5 @@ | |||
| --- | |||
| '@backstage-community/plugin-cicd-statistics': patch | |||
| @@ -0,0 +1,5 @@ | |||
| --- | |||
| '@backstage-community/plugin-bazaar': patch | |||
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
|
👋 Reminder: This Renovate major PR has been open for 21 days. Please review and merge if the changes look good. If no action is taken, this PR will be labeled |
This PR contains the following updates:
1.x→3.x^1.3.13→^3.0.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
dmtrKovalenko/date-io (@date-io/luxon)
v3.2.0Compare Source
Features
getWeekmethod by @simon-tackstrandv3.0.0Compare Source
Breaking changes:
This involves peer lib version upgrade please make sure that some underlying localised formats might be changed as well
The type inference that doesn't work with modern typescript was removed. Please make sure to upgrade typescript to v5
Changed signature of
Utils.dateand the underlying logic. Now if the value can't be parsed returns current date instead ofnull.Other changes
You can support the maintenance of this project by visiting https://github.com/sponsors/dmtrKovalenko. Your support will help us respond faster and deliver requested features. We extend our heartfelt thanks to our contributors and sponsors ❤️.
New Contributors
Full Changelog: dmtrKovalenko/date-io@v2.17.0...v3.0.0
v2.17.0Compare Source
New features
What's Changed
ES6by @LukasTy in #645DateTime.isDateTimeinstead ofinstanceofby @alex-kuck in #639New Contributors
Full Changelog: dmtrKovalenko/date-io@v2.16.1...v2.17.0
v2.16.1Compare Source
Fixes
New Contributors
Full Changelog: dmtrKovalenko/date-io@v2.16.0...v2.16.1
v2.16.0Compare Source
What's Changed
setDate/getDateby @flaviendelangle in #625Full Changelog: dmtrKovalenko/date-io@v2.15.0...v2.16.0
v2.15.0Compare Source
What's Changed
addYearsby @flaviendelangle in #623Full Changelog: dmtrKovalenko/date-io@v2.14.0...v2.15.0
v2.14.0Compare Source
What's Changed
startOfYearandendOfYearby @flaviendelangle in #614New Collaborator
Full Changelog: dmtrKovalenko/date-io@v2.13.2...v2.14.0
v2.13.2Compare Source
What's Changed
New Contributors
Full Changelog: dmtrKovalenko/date-io@v2.13.1...v2.13.2
v2.13.1Compare Source
v2.11.1Compare Source
v2.11.1
Enhancements
v2.11.0Compare Source
Features
parseISO– will parse date using library method to avoid inconsistencies between browserstoISO– will format date to iso string using libraryFixes/Enhancements
dayjsv2.10.11Compare Source
Changelog
DayJsAdapter<Dayjs>v2.10.8Compare Source
v2.10.7Compare Source
Changelog
Some bugfixes and dependency updates:
v2.10.6Compare Source
This release is finally fixing the problem of outdated builds of published
date-io/*releases.From now on versions of
@date-io/*will always be synchronized with@date-io/corepackage and will never cause version conflict or be outdated.v2.10.5Compare Source
v2.10.4Compare Source
v2.10.0Compare Source
Features
v2.9.2Compare Source
v2.9.0: 2.9.0Compare Source
Features
getDaysInMonthmethodv2.8.1Compare Source
Features
libname to the adapter interfaceFixes
v2.8.0Compare Source
v2.7.0Compare Source
Features 🎉
Fixes 🐛 | Enhancements 🧇
v2.6.0Compare Source
Breaking changes
N/A
Features
Fixes
v2.5.1Compare Source
This release is only fixing inclusivity rules of
isWithinRangemethod.v2.5.0Compare Source
Breaking changes
N/A
Features
New functions:
isWithinRange: (date: TDate, range: [TDate, TDate]) => booleanaddMonths: (date: TDate, monthCount: number) => TDatev2.4.0Compare Source
Add 2 new functions:
startOfWeek(date: TDate): TDate- returns start of weekendOfWeek(date: TDate): TDate- returns end of weekv2.3.0Compare Source
Changes
toJsDatefunction converting lib object to native js datev2.2.0Compare Source
Localization improvements release
We have changed the formats tokens to use localized formats tokens everywhere possible. Also introduced several new methods and formats
List of new methods added:
v2.1.0Compare Source
v2.0.1Compare Source
v2.0.0Compare Source
Major upgrade
Do not update if you are using @material-ui/pickers v3
Breaking changes
dateTimeFormatformatsprop and provides easy localization formattingformatmethod now has signature(date: TDate, formatKey: keyof IDateIOFormat) => stringin order to simplify formatting using new format keysformatByStringallowes to use custom (mostly user-provided) format stringsformatByString(value: TDate, formatString: string): string;Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate.