vodyani / vodyani Goto Github PK

View Code? Open in Web Editor NEW

126.0 20.0 20.0 350 KB

构建企业级 web 框架的不二之选 ✨

License: MIT License

TypeScript 99.25% Shell 0.75%

nestjs backend-server nodejs typescipt vodyani

vodyani's Introduction

Vodyani

🚀 Vodyani 是一个基于 nest.js 开发的服务端脚手架，它将是您构建 node.js 服务端项目的不二选择。

Getting started

Questions

Discussions 🧐

Team


ChoGathK

License

Vodyani is MIT licensed.

vodyani's People

Contributors

Stargazers

Watchers

Forkers

zxgmaster poke-m bobliuyang equ3fax solo-tiger-man mrhx97 hytonightyx dahuahe jinghuis chogathk nicolesherwood herpacker awekling obsidian6s zshpro mistyr0se lintl97 0x8235 n0wwa knoxnoe

vodyani's Issues

The automated release is failing 🚨

🚨 The automated release from the `8.x` 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 8.x 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:

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 `8.2.0` on branch `8.x` cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=8.1.4 <8.2.0 can be published from branch 8.x.

The following commits are responsible for the invalid release:

Merge pull request #86 from vodyani/feature/next-vodyani (3e41f20)
chore(deps): upgrade (0696845)
feat: reduce base dependencies (e265efd)
style: remove upload method 🐛 (ff83cb9)
style: code 🐛 (cfe49ae)
style: code 🐛 (e20fc84)
style: code 🐛 (6675ada)
style: code 🐛 (b3e1cc0)
style: code 🐛 (69f4a2b)
feat: change the running mode of an initiator (1b5945c)
feat: rethink the hierarchy (761e013)
docs: change site url (9aafb31)
chore(deps): change dependencies (3953234)
chore(deps): change dependencies (c2fecc7)
chore(test): add test tsconfig (b9525f0)
Merge pull request #84 from vodyani/master (000e955)
chore(license): update (65d64e3)

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

A valid branch could be master.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀

The automated release is failing 🚨

🚨 The automated release from the `8.x` 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.

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

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 `8.4.0` on branch `8.x` cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=8.3.0 <8.4.0 can be published from branch 8.x.

The following commits are responsible for the invalid release:

Merge branch 'master' into 8.x (f7c89e4)
feat: optimized frame loading speed using new versions of ark and swagger (06f5973)
Merge branch 'master' into 8.x (f95a058)
Merge pull request #86 from vodyani/feature/next-vodyani (3e41f20)

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

A valid branch could be master.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀

The automated release is failing 🚨

🚨 The automated release from the `8.x` 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.

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

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 `8.1.0` on branch `8.x` cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=8.0.1 <8.0.1 can be published from branch 8.x.

The following commits are responsible for the invalid release:

chore(ci): change workflow (99c7740)
Merge pull request #70 from vodyani/refactor/8.x (ec830ed)
chore(ci): change workflow (1fd3367)
fix: improved output style under console (05d09ec)
feat: refactor the operation mode of the service, types, definitions, methods, and dependencies (430cbb9)
feat: added a file upload example (4f772ca)
feat: add some decorators (b246b0a)
style: code (c91cc01)
feat: adapt to changes in version 8.x (700219c)
docs: update (fc0fbdb)
docs: update (bb4e8ed)
docs: update (62731e0)

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

A valid branch could be master.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀

The automated release is failing 🚨

🚨 The automated release from the `8.x` 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.

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

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 `8.4.1` on branch `8.x` cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=8.4.0 <8.4.0 can be published from branch 8.x.

The following commits are responsible for the invalid release:

fix: remove unless method (944803f)
Merge branch 'master' of github.com:vodyani/vodyani into 8.x (0b4975b)
Merge branch 'master' into 8.x (f7c89e4)
Merge branch 'master' into 8.x (f95a058)
Merge pull request #86 from vodyani/feature/next-vodyani (3e41f20)

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

A valid branch could be master.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀

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(deps): update dependency @types/supertest to v2.0.16
chore(deps): update dependency ts-node to v10.9.2
fix(deps): update dependency module-alias to v2.2.3 (module-alias, @types/module-alias)
chore(deps): update dependency @types/node to v20
chore(deps): update dependency husky to v9
chore(deps): update dependency supertest to v6.3.4 (supertest, @types/supertest)
chore(deps): update dependency typescript to v5
fix(deps): update dependency uuid to v9.0.1 (uuid, @types/uuid)
🔐 Create all rate-limited PRs at once 🔐

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

chore(deps): update commitlint monorepo to v19 (major) (@commitlint/cli, @commitlint/config-conventional)

Open

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

Detected dependencies

github-actions

.github/workflows/pr.yml

.github/workflows/release.yml

npm

package.json

@nestjs/common ^8.4.7

@nestjs/core ^8.4.7

@nestjs/platform-express 8.4.7

@vodyani/ark ^8.8.0

@vodyani/class-decorator ^8.2.3

@vodyani/core ^8.10.0

@vodyani/utils ^8.8.1

@vodyani/winston ^8.7.0

dayjs 1.11.5

lodash 4.17.21

module-alias 2.2.2

rxjs 7.5.6

uuid 9.0.0

@commitlint/cli 16.3.0

@commitlint/config-conventional 16.2.4

@nestjs/testing 8.4.7

@types/express 4.17.13

@types/jest 27.5.2

@types/lodash 4.14.182

@types/module-alias 2.0.1

@types/multer 1.4.7

@types/node 16.11.56

@types/supertest 2.0.12

@types/uuid ^8.3.4

@vodyani/eslint-config ^1.1.0

husky 7.0.4

jest 27.5.1

supertest 6.2.4

ts-jest 27.1.5

ts-node 10.9.1

typescript 4.8.2

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

todo

Refactor and match to the existing schema of User-Center
doc & code style
unit testing

vodyani / vodyani Goto Github PK

vodyani's Introduction

Vodyani

Getting started

Questions

Team

License

vodyani's People

Contributors

Stargazers

Watchers

Forkers

vodyani's Issues

🚨 The automated release from the 8.x branch failed. 🚨

The release 8.2.0 on branch 8.x cannot be published as it is out of range.

🚨 The automated release from the 8.x branch failed. 🚨

The release 8.4.0 on branch 8.x cannot be published as it is out of range.

🚨 The automated release from the 8.x branch failed. 🚨

The release 8.1.0 on branch 8.x cannot be published as it is out of range.

🚨 The automated release from the 8.x branch failed. 🚨

The release 8.4.1 on branch 8.x cannot be published as it is out of range.

Rate-Limited

Edited/Blocked

Open

Detected dependencies

Recommend Projects

Recommend Topics

Recommend Org

Jobs

🚨 The automated release from the `8.x` branch failed. 🚨

The release `8.2.0` on branch `8.x` cannot be published as it is out of range.

🚨 The automated release from the `8.x` branch failed. 🚨

The release `8.4.0` on branch `8.x` cannot be published as it is out of range.

🚨 The automated release from the `8.x` branch failed. 🚨

The release `8.1.0` on branch `8.x` cannot be published as it is out of range.

🚨 The automated release from the `8.x` branch failed. 🚨

The release `8.4.1` on branch `8.x` cannot be published as it is out of range.