Attendance-System icon indicating copy to clipboard operation
Attendance-System copied to clipboard

Update Dependencies

Open renovate[bot] opened this issue 4 years ago • 1 comments

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@chakra-ui/icons 1.0.13 -> 1.1.7 age adoption passing confidence
@chakra-ui/react (source) 1.6.3 -> 1.8.9 age adoption passing confidence
@emotion/react (source) 11.4.0 -> 11.11.1 age adoption passing confidence
@emotion/styled (source) 11.3.0 -> 11.11.0 age adoption passing confidence
@supabase/supabase-js 1.14.0 -> 1.35.7 age adoption passing confidence
date-fns 2.22.1 -> 2.30.0 age adoption passing confidence
next-runtime-dotenv 1.4.0 -> 1.5.1 age adoption passing confidence

Release Notes

chakra-ui/chakra-ui (@​chakra-ui/icons)

v1.1.7

Compare Source

Patch Changes

v1.1.6

Compare Source

Patch Changes

v1.1.5

Compare Source

Patch Changes

v1.1.4

Compare Source

Patch Changes

v1.1.3

Compare Source

Patch Changes

v1.1.2

Compare Source

Patch Changes

v1.1.1

Compare Source

Patch Changes

v1.1.0

Compare Source

Minor Changes
  • #​4991 6095eaf9a Thanks @​segunadebayo! - Update build system we use from a custom babel cli setup to preconstruct.

    The previous build system transpiles the code in src directory to dist/esm and dist/cjs keeping the same file structure. The new build system merges all files in src and transpiles to a single esm and cjs file.

    Potential Breaking Change: The side effect of this is that, if you imported any function, component or hook using the undocumented approach like import { useOutsideClick } from "@​chakra-ui/hooks/dist/use-outside-click", you'll notice that the this doesn't work anymore.

    Here's how to resolve it:

    // Won't work 🎇
    import { useOutsideClick } from "@​chakra-ui/hooks/dist/use-outside-click"
    
    // Works ✅
    import { useOutsideClick } from "@​chakra-ui/hooks"
    

    If this affected your project, we recommend that you import hooks, functions or components the way it's shown in the documentation. This will help keep your project future-proof.

Patch Changes

v1.0.17

Compare Source

Patch Changes

v1.0.16

Compare Source

Patch Changes

v1.0.15

Compare Source

Patch Changes

v1.0.14

Compare Source

Patch Changes
chakra-ui/chakra-ui (@​chakra-ui/react)

v1.8.8

Compare Source

Patch Changes

v1.8.7

Compare Source

Patch Changes

v1.8.6

Compare Source

Patch Changes

v1.8.5

Compare Source

Patch Changes

v1.8.4

Compare Source

Patch Changes

v1.8.3

Compare Source

Patch Changes

v1.8.2

Compare Source

Patch Changes

v1.8.1

Compare Source

Patch Changes

v1.8.0

Compare Source

Minor Changes
Patch Changes

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Asia/Singapore, 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.


  • [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

renovate[bot] avatar Jun 18 '21 17:06 renovate[bot]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: npm-shrinkwrap.json
npm notice 
npm notice New major version of npm available! 8.19.4 -> 9.7.1
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.7.1>
npm notice Run `npm install -g [email protected]` to update!
npm notice 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"17.0.2" from the root project
npm ERR!   peer react@">=16.8.6" from @chakra-ui/[email protected]
npm ERR!   node_modules/@chakra-ui/icons
npm ERR!     @chakra-ui/icons@"1.1.7" from the root project
npm ERR!   2 more (@emotion/react, @emotion/styled)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@">=18" from @chakra-ui/[email protected]
npm ERR! node_modules/@chakra-ui/system
npm ERR!   peer @chakra-ui/system@">=1.0.0" from @chakra-ui/[email protected]
npm ERR!   node_modules/@chakra-ui/icons
npm ERR!     @chakra-ui/icons@"1.1.7" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/worker/24cbca/b864bd/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/worker/24cbca/b864bd/cache/others/npm/_logs/2023-06-10T05_58_17_389Z-debug-0.log

renovate[bot] avatar May 15 '22 20:05 renovate[bot]