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

Version mismatch

The pom.xml version of 3.1.9-SNAPSHOT differs too much from last git tag version of 3.1.9.

Please edit the project entry in the pom.xml file to have a version number of no more than 1 patch version ahead of the git tag version of 3.1.9.

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.

Pending Approval

These branches will be created by Renovate only once you click their checkbox below.

• build(deps): update codecov/codecov-action action to v3.1.4
• build(deps): update logerfo/gitflow-action action to v0.0.5
• build(deps): update dependency org.apache.commons:commons-lang3 to v3.13.0
• build(deps): update dependency org.codehaus.mojo:license-maven-plugin to v2.2.0
• build(deps): update dependency conventional-changelog-conventionalcommits to v6
• build(deps): update dependency patch-package to v8
• build(deps): update dependency semantic-release to v21
• 🔐 Create all pending approval PRs at once 🔐

Rate-Limited

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

• build(deps): update plugin.license.version to v4.2 (com.mycila:license-maven-plugin-git, com.mycila:license-maven-plugin)

Open

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

• build(deps): update dependency @semantic-release/changelog to v6.0.3
• build(deps): update dependency org.apache.maven.plugins:maven-resources-plugin to v3.3.1
• build(deps): update dependency org.jacoco:jacoco-maven-plugin to v0.8.10
• build(deps): update dependency patch-package to v6.5.1
• build(deps): update dependency io.ktor:ktor-bom to v2.3.3
• build(deps): update dependency maven to v3.9.4
• build(deps): update dependency maven-wrapper to v3.2.0
• build(deps): update dependency org.apache.maven.plugins:maven-enforcer-plugin to v3.3.0
• build(deps): update dependency org.apache.maven.plugins:maven-javadoc-plugin to v3.5.0
• build(deps): update dependency org.jetbrains.kotlin:kotlin-bom to v1.9.0
• build(deps): update wagoid/commitlint-github-action action to v5.4.3
• 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

Feature Request

Добавить файл CODEOWNERS

Опишите Предпочтительное Решение

Добавить файл CODEOWNERS с содержимым:

* @xzima

Feature Request

Опишите Feature Request

Хочу сконфигурировать шаблоны задач.

Опишите Предпочтительное Решение

Добавить папку ISSUE_TEMPLATE с шаблонами задач на багу и фичу

Опишите Альтернативные Решения

Related Code

Дополнительный контекст

Feature Request

• добавить интеграцию codecov
• добавить бейдж

Дополнительная информация

https://app.codecov.io/gh/xzima

Feature Request

Переделать валидацию комитов на более сложную с использованием semantic-pull-requests.

Разбить процесс релиза с процессом проверки PR

Feature Request

Опишите Feature Request

Обновить package.json

Опишите Предпочтительное Решение

• удалить не используемые скрипты
• исправить версии зависимостей на точные значения