Skip to content

chore: mention mise and aqua in the readme #409

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 22, 2025

Conversation

mrazauskas
Copy link
Contributor

Please, consider mentioning mise and aqua in the readme.

Reference: jsonschema was recently added to the aqua (aquaproj/aqua-registry#39066) and mise (jdx/mise#5714) registries.


Thanks for this project! I was looking for a tool like this one for some time.

@mrazauskas mrazauskas force-pushed the mention-mise-and-aqua branch from 11a6372 to dafb107 Compare July 21, 2025 14:05
### From mise

```sh
mise use jsonschema
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting. I never hears about these package managers. Are they specifically integrating with this tool? Might be worth putting a link to their homepages and the manifests that they have created for this tool, if any?

@mrazauskas
Copy link
Contributor Author

For the context, I use mise on daily basis. And mise is using registry from aqua. (It can also install from cargo, pip, npm or directly from GitHub releases and so on. These are known as different Backends.)

To make mise use jsonschema work, I had to include jsonschema to the aqua registry first. Although I do not use it.

The idea was to add just a short note that jsonschema is available from these tools as well. We can add links, of course. I was thinking, these notes only make sense for users of mise or aqua.

@jviotti
Copy link
Member

jviotti commented Jul 22, 2025

Nice! Sounds very interesting indeed. If you can add a link to the mise manifest in the aqua registry, that'd be great. At least so anybody can easily find it and update it, etc when needed. Maybe something like: "This tool is available on mise (link to mise in case people are curious to learn more) through the aqua registry (link to the registry entry) since v10.0.0 (or whatever)"

Signed-off-by: mrazauskas <tom@mrazauskas.de>
@mrazauskas mrazauskas force-pushed the mention-mise-and-aqua branch from dafb107 to 314f9fb Compare July 22, 2025 13:11
@mrazauskas
Copy link
Contributor Author

If you can add a link to the mise manifest in the aqua registry, that'd be great.

Yes but.. (; I was thinking to add the pipx registry entry to the mise manifest as well. Have to try it first, of course. And the story is changing.

For me it seems that all this are only implementation details, or?

@jviotti
Copy link
Member

jviotti commented Jul 22, 2025

Yeah, no worries. We can merge and feel free to send follow up PRs updating the docs if you want!

@jviotti jviotti merged commit bab7e21 into sourcemeta:main Jul 22, 2025
11 checks passed
@jviotti
Copy link
Member

jviotti commented Jul 22, 2025

Merged! Thanks a lot @mrazauskas. Out of curiosity, what are you using the tool for?

@mrazauskas mrazauskas deleted the mention-mise-and-aqua branch July 22, 2025 14:12
@mrazauskas
Copy link
Contributor Author

Great!


I use jsonschema to test a schema that is generate by a JS script and emitted using JSON.stringify(). Obviously needs tests. Even if that is a simple schema.

Your approach of schema tests is exactly what I was looking for some time. The tests live here.

By the way, jsonschema and mise saved few seconds of CI runs in my project. This is another win!

@jviotti
Copy link
Member

jviotti commented Jul 22, 2025

That's amazing to hear 🚀 . If you have any feature requests around JSON Schema, just let me know. We are always trying to get more feedback from real-world use cases like yours.

tmeijn pushed a commit to tmeijn/dotfiles that referenced this pull request Aug 6, 2025
⚠️ **CAUTION: this is a major update, indicating a breaking change!** ⚠️

This MR contains the following updates:

| Package | Update | Change |
|---|---|---|
| [sourcemeta/jsonschema](https://github.com/sourcemeta/jsonschema) | major | `v10.0.0` -> `v11.0.0` |

MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot).

**Proposed changes to behavior should be submitted there as MRs.**

---

### Release Notes

<details>
<summary>sourcemeta/jsonschema (sourcemeta/jsonschema)</summary>

### [`v11.0.0`](https://github.com/sourcemeta/jsonschema/releases/tag/v11.0.0)

[Compare Source](sourcemeta/jsonschema@v10.0.0...v11.0.0)

#### What's Changed

- Deploy CLI binaries to PyPI by [@&#8203;jviotti](https://github.com/jviotti) in sourcemeta/jsonschema#407
- Mention the `mise` package manager in the README by [@&#8203;mrazauskas](https://github.com/mrazauskas) in sourcemeta/jsonschema#409
- Implement new linting rules (`additional_items_with_schema_items`, `draft_official_dialect_without_empty_fragment`, `else_empty`, `then_empty`, and `modern_official_dialect_with_empty_fragment`) [@&#8203;jviotti](https://github.com/jviotti) in sourcemeta/jsonschema#410
- Add new linting rules around `propertyNames` by [@&#8203;jviotti](https://github.com/jviotti) in sourcemeta/jsonschema#413
- Implement new linting rules (`draft_ref_siblings` and `equal_numeric_bounds_to_const`) by [@&#8203;jviotti](https://github.com/jviotti) in sourcemeta/jsonschema#414
- Extend the scope of the `non_applicable_type_specific_keywords` linting rule to cover `const` and `enum` by [@&#8203;jviotti](https://github.com/jviotti) in sourcemeta/jsonschema#414
- Stop moving all unknown keywords to the bottom of the schemas in `fmt` by [@&#8203;jviotti](https://github.com/jviotti) in sourcemeta/jsonschema#414
- Provide better error messages on relative meta-schema references by [@&#8203;jviotti](https://github.com/jviotti) in sourcemeta/jsonschema#415
- Minor revisions to schema locations in `inspect --json` by [@&#8203;jviotti](https://github.com/jviotti) in sourcemeta/jsonschema#415

#### New Contributors

- [@&#8203;mrazauskas](https://github.com/mrazauskas) made their first contribution in sourcemeta/jsonschema#409

**Full Changelog**: sourcemeta/jsonschema@v10.0.0...v11.0.0

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this MR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box

---

This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS41MS4xIiwidXBkYXRlZEluVmVyIjoiNDEuNTEuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiUmVub3ZhdGUgQm90Il19-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants