snowball-tech / fractal Goto Github PK

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• chore(deps): lock file maintenance

Pending Status Checks

These updates await pending status checks. To force their creation now, click the checkbox below.

• dev-deps: update dependency @types/eslint to v8.56.6
• dev-deps: update dependency chromatic to v11.1.1
• dev-deps: update dependency postcss to v8.4.37
• dev-deps: update storybook monorepo to v8.0.2 (patch) (@storybook/addon-a11y, @storybook/addon-actions, @storybook/addon-essentials, @storybook/addon-interactions, @storybook/addon-links, @storybook/blocks, @storybook/components, @storybook/manager-api, @storybook/preview-api, @storybook/react, @storybook/react-vite, @storybook/test, @storybook/theming, storybook)
• dev-deps: update dependency chromatic to v11.2.0
• dev-deps: update dependency vite to v5.2.2

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• dev-deps: update dependency @types/node to v20.11.30

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• chore(deps): update lewagon/wait-on-check-action action to v1.3.3
• chore(deps): update actions/labeler action to v5
• chore(deps): update actions/stale action to v9
• chore(deps): update node.js to v20

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Thanks for this design system, I'm excited to give it a try! I'm not yet able to successfully get any components working.

I created a new Vite + React app and imported the package according to the docs, but when I start a development server the components don't render properly. Here I have a switch, button, and paper but none are rendered:

<Switch label="test" switchPosition="right" />

<Button label="chewie" variant="display" />

<Paper elevation="1">
  Size matters not. Look at me. Judge me by my size, do you? Hmm? Hmm.
  And well you should not. For my ally is the Force, and a powerful ally
  it is. Life creates it, makes it grow. Its energy surrounds us and
  binds us. Luminous beings are we, not this crude matter. You must feel
  the Force around you; here, between you, me, the tree, the rock,
  everywhere, yes. Even between the land and the ship.
</Paper>

I can't seem to understand what's missing yet, but it could be that this @snowball-tech/fractal-panda package doesn't exist publicly yet?

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Cannot push to the Git repository.

semantic-release cannot push the version tag to the branch main on the remote Git repository with URL https://[secure]@github.com/snowball-tech/fractal.git.

This can be caused by:

• a misconfiguration of the repositoryUrl option
• the repository being unavailable
• or missing push permission for the user configured via the Git credentials on your CI environment

Good luck with your project ✨

Your semantic-release bot 📦🚀