kit-p / json-kit Goto Github PK

Current Stage

Released - Feature Complete

Tasks

• Initialize the project (#3)
• Setup unit tests (#3)
• Setup CI/CD (#15) (#16) (#18) (#19) (#20) (#21) (#26) (#27) (#29)
• Setup automatic dependency updates (#37) (#39)
• Setup documentations (#45)
• Implement JSON conversion from/to string (#6) (#13)
• Implement Extended JSON conversion from/to string (#6) (#13)
• Implement conversion between JSON and Extended JSON (#42)
• Implement JSON minification and restoration (#6) (#13)
• Implement Extended JSON minification and restoration (#6) (#13)
• Implement JSON compression and decompression (#7) (#13)
• Implement Extended JSON compression and decompression (#7) (#13)

---

Thank you for visiting here, feel free to star this repository to support my development!

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

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• chore(deps): update commitlint monorepo to v17.6.7 (@commitlint/cli, @commitlint/config-conventional)
• chore(deps): update dependency @types/node to v20.4.7
• chore(deps): update dependency prettier to v3.0.1
• chore(deps): update dependency terser to v5.19.2
• chore(deps): update dependency tslib to v2.6.1
• chore(deps): update dependency typedoc-plugin-markdown to v3.15.4
• chore(deps): update jest monorepo to v29.6.2 (@jest/globals, jest)
• chore(deps): update pnpm to v8.6.11
• chore(deps): update swc monorepo (@swc/core, @swc/jest)
• chore(deps): update dependency eslint to v8.46.0
• chore(deps): update dependency eslint-config-prettier to v8.10.0
• chore(deps): update dependency renovate to v36.33.4
• chore(deps): update dependency rollup to v3.27.2
• chore(deps): update typescript-eslint monorepo to v6.2.1 (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• fix(deps): update dependency bson to v5

Pending Status Checks

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

• chore(deps): update dependency eslint-config-prettier to v9

Detected dependencies

github-actions

.github/workflows/publish.yml

• actions/checkout v3
• actions/setup-node v3
• pnpm/action-setup v2
• actions/cache v3
• Andrew-Chen-Wang/github-wiki-action v4
• actions/upload-pages-artifact v2
• actions/configure-pages v3
• actions/deploy-pages v2

.github/workflows/release.yml

• actions/checkout v3
• actions/setup-node v3
• pnpm/action-setup v2
• actions/cache v3

npm

package.json

• bson ^4.7.2
• js-base64 ^3.7.5
• lodash.clonedeep ^4.5.0
• lz4js ^0.2.0
• @commitlint/cli 17.6.6
• @commitlint/config-conventional 17.6.6
• @jest/globals 29.6.1
• @rollup/plugin-commonjs 25.0.3
• @rollup/plugin-node-resolve 15.1.0
• @rollup/plugin-typescript 11.1.2
• @semantic-release/changelog 6.0.3
• @semantic-release/exec 6.0.3
• @semantic-release/git 10.0.1
• @semantic-release/npm 10.0.4
• @swc/core 1.3.69
• @swc/jest 0.2.26
• @tsconfig/node-lts 18.12.3
• @types/jest 29.5.3
• @types/lodash.clonedeep 4.5.7
• @types/node 20.4.2
• @typescript-eslint/eslint-plugin 6.0.0
• @typescript-eslint/parser 6.0.0
• concurrently 8.2.0
• eslint 8.45.0
• eslint-config-prettier 8.8.0
• husky 8.0.3
• jest 29.6.1
• prettier 3.0.0
• renovate 36.8.11
• rollup 3.26.2
• semantic-release 21.0.7
• terser 5.19.0
• ts-jest 29.1.1
• tslib 2.6.0
• typedoc 0.24.8
• typedoc-github-wiki-theme 1.1.0
• typedoc-plugin-markdown 3.15.3
• typescript 5.1.6
• node >=18
• pnpm ^8.6.7
• pnpm 8.6.7

---

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

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Cannot find preset's package (mergeConfidence:all-badges)

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