pustovitdmytro / fatum-vscode

Random data generator

💻 My Github account statistics:

🏢 I'm currently working at the WebbyLab

📫 How to reach me:

• telegram: @dimapustovit
• email: [email protected]
• skype: dima.pustovit

fatum-vscode's Issues

Dependency Dashboard

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: update actions/checkout action to v4

Open

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

• Chore: Update devDependencies (non-major) (@babel/cli, @babel/core, @babel/node, @babel/plugin-proposal-decorators, @babel/plugin-proposal-object-rest-spread, @babel/plugin-proposal-optional-chaining, @babel/preset-env, @babel/runtime, @commitlint/cli, @commitlint/lint, @semantic-release/changelog, @types/estree, @types/mocha, @types/node, @types/vscode, @typescript-eslint/eslint-plugin, @typescript-eslint/parser, chai, chance, danger, eslint, eslint-config-incredible, eslint-plugin-censor, eslint-plugin-import, eslint-plugin-markdown, eslint-plugin-mocha, eslint-plugin-regexp, eslint-plugin-security, eslint-plugin-sonarjs, fs-extra, glob, husky, jscpd, lockfile-lint, mocha-junit-reporter, semantic-release-telegram, semantic-release-vsce, ts-loader, typescript, uuid, webpack, webpack-cli)
• Upgrade: Update dependency winston to v3.10.0
• Chore: Update devDependencies (non-major) (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser, babel-plugin-module-resolver, conventional-changelog-eslint, eslint-plugin-unicorn, semantic-release)
• chore: update actions/setup-node action to v3
• Chore: Lock file maintenance
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

github-actions

.github/workflows/codeql.yml

• actions/checkout v3
• github/codeql-action v2
• github/codeql-action v2
• github/codeql-action v2

.github/workflows/npt.yml

• actions/checkout v2
• actions/setup-node v2
• actions/setup-node v2

npm

package.json

• cottus 1.10.13
• fatum 1.1.0
• myrmidon 1.8.1
• winston 3.9.0
• winston-vscode 1.0.0
• @babel/cli ^7.19.3
• @babel/core ^7.20.5
• @babel/node ^7.20.5
• @babel/plugin-proposal-class-properties ^7.18.6
• @babel/plugin-proposal-decorators ^7.20.5
• @babel/plugin-proposal-object-rest-spread ^7.20.2
• @babel/plugin-proposal-optional-chaining ^7.18.9
• @babel/polyfill ^7.12.1
• @babel/preset-env ^7.20.2
• @babel/runtime ^7.20.6
• @commitlint/cli ^17.3.0
• @commitlint/lint ^17.3.0
• @semantic-release/changelog ^6.0.2
• @semantic-release/git ^10.0.1
• @types/estree ^1.0.1
• @types/glob ^8.1.0
• @types/mocha ^10.0.1
• @types/node ^20.1.0
• @types/vscode ^1.78.0
• @typescript-eslint/eslint-plugin ^5.59.2
• @typescript-eslint/parser ^5.59.2
• babel-plugin-module-resolver ^4.1.0
• chai ^4.3.7
• chance ^1.1.9
• conventional-changelog-eslint ^3.0.9
• coveralls ^3.1.1
• danger ^11.2.0
• eslint ^8.30.0
• eslint-config-incredible ^2.4.2
• eslint-plugin-censor ^1.5.2
• eslint-plugin-import ^2.26.0
• eslint-plugin-markdown ^3.0.0
• eslint-plugin-mocha ^10.1.0
• eslint-plugin-no-secrets ^0.8.9
• eslint-plugin-node ^11.1.0
• eslint-plugin-promise ^6.1.1
• eslint-plugin-regexp ^1.11.0
• eslint-plugin-scanjs-rules ^0.2.1
• eslint-plugin-security ^1.5.0
• eslint-plugin-sonarjs ^0.17.0
• eslint-plugin-unicorn 42.0.0
• fs-extra ^11.1.0
• glob ^10.2.2
• husky ^8.0.2
• jscpd ^3.5.3
• lockfile-lint ^4.9.6
• mocha ^10.2.0
• mocha-junit-reporter ^2.2.0
• node-package-tester ^1.3.6
• nyc ^15.1.0
• semantic-release ^19.0.5
• semantic-release-telegram ^1.6.0
• semantic-release-vsce ^5.5.9
• source-map-support ^0.5.21
• ts-loader ^9.4.2
• typescript ^5.0.4
• uuid ^9.0.0
• vsce ^2.15.0
• vscode-test ^1.6.1
• webpack ^5.82.0
• webpack-cli ^5.1.0
• vscode ^1.78.0
• node >=10

---

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

The automated release is failing 🚨

🚨 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.

---

Invalid vsce personal access token. Additional information:

Error: Command failed with exit code 1: vsce verify-pat
ERROR Can not read the publisher's name. Either supply it as an argument or run vsce from the extension folder. Additional information:

Error: Manifest needs the 'activationEvents' property, given it has a 'main' property.

Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the semantic-release-vsce plugin to add more helpful information.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀