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

Pending Status Checks

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

• chore(npm): update dependency stylelint to v16.9.0
• chore(npm): update pnpm to v9.9.0

Open

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

• chore(npm): update @3846masa/configs digest to 4705f5c
• fix(npm): update dependency @mdn/browser-compat-data to v5.5.48
• chore(npm): update dependency rimraf to v6
• chore(npm): update semantic-release monorepo (major) (@semantic-release/commit-analyzer, @semantic-release/npm, @semantic-release/release-notes-generator, semantic-release)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

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

Hello @3846masa, 👋🏼

Thank you for creating the excellent package!

In this issue, I recommend adding the repository field to package.json. If added, npm view or npm repo will be much more helpful. For example:

$ npm view 'stylelint-browser-compat' repository

$ npm view 'stylelint' repository
{ type: 'git', url: 'git+https://github.com/stylelint/stylelint.git' }

$ npm repo --browser=false 'stylelint-browser-compat'
npm error no repository
npm error A complete log of this run can be found in: /Users/masafumi.koba/.npm/_logs/2024-07-12T02_52_40_138Z-debug-0.log

$ npm repo --browser=false 'stylelint'
stylelint repo available at the following URL:
https://github.com/stylelint/stylelint

It would be great if you could consider it. Thank you. 😃

🚨 The automated release from the develop 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 develop 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 📦🚀

After v1.0.0-beta.122, we encounter the error below on running stylelint.

TypeError: Cannot read properties of undefined (reading '__compat')
    at /home/runner/work/web/web/node_modules/.pnpm/[email protected][email protected][email protected][email protected]_/node_modules/stylelint-browser-compat/lib/rule.js:56:19
    at async Promise.all (index 0)

I think this change may affects.
820c73f#diff-0ceba63778a81ad3c2b980db18fb8c18cb54fb02b1f892290608b7eaa5fbb177

Environment

• Node.js 20.12.2
• pnpm 9.1.3
• stylelint 16.6.1