lobehub / dumi-theme-lobehub Goto Github PK

💻 系统环境 | Operating System

Windows

🌐 浏览器 | Browser

Chrome

🐛 问题描述 | Bug Description

Readme 中的安装方式写的不对，现在写的是
pnpm add dumi-theme-antd-style -D

🚦 期望结果 | Expected Behavior

应该是
pnpm add dumi-theme-lobehub -D

📷 复现步骤 | Recurrence Steps

访问该地址就知道了 https://github.com/lobehub/dumi-theme-lobehub#:~:text=pnpm%20add%20dumi%2Dtheme%2Dantd%2Dstyle%20%2DD

📝 补充信息 | Additional Information

No response

调整下README.md的installation的内容；
仓库不是叫 dumi-theme-lobehub 这个嘛，
目前是 xxx-antd-style;

🚨 The automated release from the master 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 master 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.

The release 1.6.0 on branch master cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=1.5.0 <1.6.0 can be published from branch master.

The following commits are responsible for the invalid release:

• 💄 style: Update Markdown style (e39802f)
• ✨ feat: Add favicons and metadata to web page using Helmet component (5b8dccf)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch master with git revert or git reset.

A valid branch could be main.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀

💻 系统环境 | Operating System

Windows

🌐 浏览器 | Browser

Chrome

🐛 问题描述 | Bug Description

export default { themeConfig: { // 配置高清方案，默认为 750 高清方案 hd: { rules: [...], }, // 配置 demo 预览器的设备宽度，默认为 375px deviceWidth: 375, }, }
不能像官网一样的样式生效： https://d.umijs.org/guide/mobile-library#%E6%95%88%E6%9E%9C%E9%A2%84%E8%A7%88

🚦 期望结果 | Expected Behavior

No response

📷 复现步骤 | Recurrence Steps

No response

📝 补充信息 | Additional Information

No response

💻 系统环境 | Operating System

Windows

🌐 浏览器 | Browser

Chrome & edge

🐛 问题描述 | Bug Description

🚦 期望结果 | Expected Behavior

No response

📷 复现步骤 | Recurrence Steps

No response

📝 补充信息 | Additional Information

No response

💻 系统环境 | Operating System

macOS

🌐 浏览器 | Browser

Chrome

🐛 问题描述 | Bug Description

黑暗模式下，每次进入页面的时候，都回会先闪烁一下浅色模式，然后再切换回暗色模式

🚦 期望结果 | Expected Behavior

黑暗模式下，每次进入页面的时候，都不要出现闪烁

📷 复现步骤 | Recurrence Steps

访问这个页面https://dumi-theme.lobehub.com/components/action-icon，然后切换到黑暗模式，刷新页面即可复现

📝 补充信息 | Additional Information

No response

🚨 The automated release from the master 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 master 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.

The release 1.6.0 on branch master cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=1.5.0 <1.6.0 can be published from branch master.

The following commits are responsible for the invalid release:

• 🐛 fix: Lock dumi to 2.2.17 (6ed7234)
• 💄 style: Update Markdown style (e39802f)
• ✨ feat: Add favicons and metadata to web page using Helmet component (5b8dccf)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch master with git revert or git reset.

A valid branch could be main.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀

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

Open

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

• Update dependency dumi to ~2.2 || ~2.4.0
• Update dependency father to v4.4.4
• Update dependency eslint to v9
• Update dependency jsdom to v24
• Update dependency lint-staged to v15
• Update dependency semantic-release to v24
• Update dependency stylelint to v16
• Update oven-sh/setup-bun action to v2
• Click on this checkbox to rebase all open PRs at once

Ignored or Blocked

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

• Update dependency chalk to v5
• Update dependency remark to v15
• Update dependency remark-cli to v12

Detected dependencies

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

💻 系统环境 | Operating System

Windows

🌐 浏览器 | Browser

Chrome

🐛 问题描述 | Bug Description

一直显示未 lobehub

🚦 期望结果 | Expected Behavior

No response

📷 复现步骤 | Recurrence Steps

No response

📝 补充信息 | Additional Information

No response