takanome-dev / assign-issue-action Goto Github PK

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

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update dependency eslint to v9
• chore(deps): update dependency eslint-plugin-jest to v28
• 🔐 Create all rate-limited PRs at once 🔐

Open

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

• chore(deps): update babel monorepo (@babel/preset-env, @babel/preset-typescript)
• chore(deps): update dependency @types/node to v18.19.32
• chore(deps): update dependency ts-jest to v29.1.2
• chore(deps): update dependency lint-staged to v15.2.2
• chore(deps): update dependency prettier to v3.2.5
• chore(deps): update typescript-eslint monorepo to v7.8.0 (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• chore(deps): update actions/checkout action to v4
• chore(deps): update codecov/codecov-action action to v4
• chore(deps): update dependency husky to v9
• chore(deps): update geekyeggo/delete-artifact action to v5
• 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.

• chore(deps): update node.js to v20 (node, @types/node)
• chore(deps): update npm to v10

Detected dependencies

github-actions

.github/workflows/codeql-analysis.yml

• actions/checkout v4
• actions/setup-node v4
• github/codeql-action v3
• github/codeql-action v3

.github/workflows/development.yml

• actions/checkout v3
• actions/setup-node v4
• bahmutov/npm-install v1
• codecov/codecov-action v3
• actions/checkout v3
• actions/setup-node v4
• bahmutov/npm-install v1
• actions/checkout v3
• actions/setup-node v4
• bahmutov/npm-install v1

.github/workflows/release.yml

• actions/checkout v3
• actions/setup-node v4
• bahmutov/npm-install v1
• actions/upload-artifact v4
• actions/checkout v3
• actions/download-artifact v4
• geekyeggo/delete-artifact v4

npm

package.json

• @actions/core ^1.10.1
• @actions/github ^6.0.0
• mustache ^4.2.0
• @babel/preset-env 7.24.0
• @babel/preset-typescript 7.23.3
• @types/jest 29.5.12
• @types/js-yaml 4.0.9
• @types/mustache 4.2.5
• @types/node 18.19.24
• @typescript-eslint/eslint-plugin ^7.0.0
• @typescript-eslint/parser 7.5.0
• @vercel/ncc 0.38.1
• eslint 8.57.0
• eslint-plugin-github 4.10.2
• eslint-plugin-jest 27.9.0
• eslint-plugin-prettier ^5.0.0
• husky 8.0.3
• jest 29.7.0
• js-yaml 4.1.0
• lint-staged 15.1.0
• prettier 3.1.1
• ts-jest 29.1.1
• typescript 5.4.5
• node 18.x
• npm 9.x

---

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

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

---

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

What would you like to share?

Hello,

Is it possible to change assigned_comment and already_assigned_comment author. It is set to repo owner at the moment and we (WordPress Documentation team) would love to make it obvious it is a bot. Thanks

Additional information

No response

Would you like to work on this issue?

• Yes, I want to work on this issue!

Code of Conduct

• I agree to follow this project's Code of Conduct