mui-x
mui-x copied to clipboard
mui
Bump dayjs to ^1.11.13
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| dayjs (source) | ^1.11.11 -> ^1.11.13 |
Release Notes
Configuration
📅 Schedule: Branch creation - "on sunday before 6:00am" in timezone 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.
🔕 Ignore: Close this PR and you won't be reminded about these updates 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[bot] avatar](https://avatars.githubusercontent.com/in/2740?v=4 "Published by a pub.dev verified publisher"){kind=small}
Deploy preview: https://deploy-preview-13919--material-ui-x.netlify.app/
Generated by :no_entry_sign: dangerJS against 511d6cb7aabe8ea560cdbbc60602fdf031d7dd8c
This pull request has conflicts, please resolve those before we can evaluate the pull request.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This pull request has conflicts, please resolve those before we can evaluate the pull request.
This pull request has conflicts, please resolve those before we can evaluate the pull request.
This pull request has conflicts, please resolve those before we can evaluate the pull request.
It seems to fix #9653
We need to test it in depth to make sure it does
But if it does, I'm in favor of bumping the minimal version of dayjs supported in the next major (maybe wait 2 months to make sure there is no massive regression introduced by this version).
Edited/Blocked Notification
Renovate 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.
⚠️ Warning: custom changes will be lost.
We need to test it in depth to make sure it does But if it does, I'm in favor of bumping the minimal version of
dayjssupported in the next major (maybe wait 2 months to make sure there is no massive regression introduced by this version).
@flav Do you think their (dayjs) fix makes sense, especially given other library behaviors?
Is it fine that any date with a +00:00 offset will internally be handled as a UTC date? 🤔
Is it fine that any date with a +00:00 offset will internally be handled as a UTC date? 🤔
I have my doubts, but not enough knowledge to know if this will cause problem or not Hopefully not, but that's why I'd wait for the end of the alpha before bumping the dep.
Hopefully not, but that's why I'd wait for the end of the alpha before bumping the dep.
Gotcha. Just confirming. Do you mean the peer dep?
We can clearly keep that bump for later. 👌