Skip to content
This repository has been archived by the owner on Jan 2, 2024. It is now read-only.

Update: dependencies 🆙 (major) #393

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 1, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
componentry 5.0.0 -> 7.1.0 age adoption passing confidence
prism-react-renderer 1.3.5 -> 2.0.6 age adoption passing confidence

Release Notes

crystal-ball/componentry (componentry)

v7.1.0

Compare Source

v7.0.0: 🚀 - Useful utilities

Compare Source

What's Changed

BREAKING đź’Ą

  • createUtilityClasses has been renamed to createUtilityProps. The return value has been updated to return { filteredProps, utilityClassName, and utilityStyle }
  • initializeUtilityClassesTheme has been renamed to initializeUtilityPropsTheme

Full Changelog: crystal-ball/componentry@v6.5.0...v7.0.0

v6.5.0

Compare Source

What's Changed

Full Changelog: crystal-ball/componentry@v6.4.0...v6.5.0

v6.4.0

Compare Source

What's Changed

Full Changelog: crystal-ball/componentry@v6.3.0...v6.4.0

v6.3.0

Compare Source

What's Changed

Full Changelog: crystal-ball/componentry@v6.2.0...v6.3.0

v6.2.0

Compare Source

What's Changed

Full Changelog: crystal-ball/componentry@v6.1.0...v6.2.0

v6.1.0

Compare Source

What's Changed

Full Changelog: crystal-ball/componentry@v6.0.0...v6.1.0

v6.0.0: 🚀 - Babel Precompiling

Compare Source

v6 of Componentry provides a feature that has been in the works for a long time: Precompiling components with Babel 🏎 🎉

The display components Block, Flex, Grid, Paper, and Text now have full support for precompilation with Babel at build time. By compiling these components to static DOM elements with classNames applications can use flexible design system components with helpful guardrails with zero runtime overhead

Breaking changes

The configuration shape for ComponentryProvider and componentry.config.js is updated to support precompilation configurations. The exported Config shape should be used for both (note all fields are optional)

A common setup might look like:

componentry.config.js
const { theme } = require('./src/theme/theme')
const { textStyles } = require('./src/components/Text/Text/styles')

module.exports = {
  theme,
  styles: {
    Text: textStyles
  }
}
app.js
import { ComponentryProvider } from 'componentry'
import { theme } from './theme/theme'
import { textProps } from './components/Text/Text'

const componentryConfig = {
  theme,
  defaultProps: {
    Text: textProps
  }
}

root.render(
  <ComponentryProvider config={componentryConfig>
    <App />
  </ComponentryProvider>
)

What's Changed

Full Changelog: crystal-ball/componentry@v5.0.1...v6.0.0

v5.0.1

Compare Source

What's Changed

Full Changelog: crystal-ball/componentry@v5.0.0...v5.0.1

FormidableLabs/prism-react-renderer (prism-react-renderer)

v2.0.6

Compare Source

Patch Changes

v2.0.5

Compare Source

Patch Changes
  • Fixed bug where an undefined theme would cause a runtime error.
    (#​213)

v2.0.4

Compare Source

Patch Changes

v2.0.3

Compare Source

Patch Changes

v2.0.2

Compare Source

Patch Changes

v2.0.1

Compare Source

Patch Changes

v2.0.0

Compare Source

Major Changes
Minor Changes
  • Added 2 new styles for the code viewer. light & dark mode themes using only
    (#​192)
    colors found on tailwindCSS.

Configuration

đź“… Schedule: Branch creation - "before 3am on the first day of the month" (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.


  • 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 renovate bot requested a review from DHedgecock as a code owner October 1, 2022 01:07
@renovate renovate bot added the Renovate label Oct 1, 2022
@renovate renovate bot force-pushed the renovate/major-dependencies branch from 1fff386 to 39f3cf5 Compare November 20, 2022 11:46
@renovate renovate bot force-pushed the renovate/major-dependencies branch from 39f3cf5 to e437731 Compare March 16, 2023 08:04
@renovate renovate bot changed the title Update: Project componentry to v6 🆙 Update: Project componentry to v7 🆙 Mar 16, 2023
@renovate
Copy link
Contributor Author

renovate bot commented Mar 16, 2023

âš  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: package-lock.json
npm notice 
npm notice New major version of npm available! 8.19.4 -> 9.7.2
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.7.2>
npm notice Run `npm install -g npm@9.7.2` to update!
npm notice 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @crystal-ball/react-app-prototype@1.0.0
npm ERR! Found: postcss@8.4.14
npm ERR! node_modules/postcss
npm ERR!   dev postcss@"8.4.14" from the root project
npm ERR!   peer postcss@"8" from componentry@7.1.0
npm ERR!   node_modules/componentry
npm ERR!     componentry@"7.1.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer postcss@"^8.4.21" from postcss-js@4.0.1
npm ERR! node_modules/postcss-js
npm ERR!   peer postcss-js@"4" from componentry@7.1.0
npm ERR!   node_modules/componentry
npm ERR!     componentry@"7.1.0" 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/d900f0/fe0e65/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/d900f0/fe0e65/cache/others/npm/_logs/2023-06-26T15_12_46_238Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-dependencies branch from e437731 to abe0589 Compare May 28, 2023 10:05
@renovate renovate bot changed the title Update: Project componentry to v7 🆙 Update: dependencies 🆙 (major) May 28, 2023
@renovate renovate bot force-pushed the renovate/major-dependencies branch from abe0589 to 376eeb6 Compare June 8, 2023 18:05
@renovate renovate bot force-pushed the renovate/major-dependencies branch from 376eeb6 to b4d7b52 Compare June 26, 2023 15:12
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants