Dockerfile: also disable SIMD support on Docker binaries as well#526
Merged
jviotti merged 1 commit intosourcemeta:mainfrom Oct 30, 2025
Merged
Dockerfile: also disable SIMD support on Docker binaries as well#526jviotti merged 1 commit intosourcemeta:mainfrom
jviotti merged 1 commit intosourcemeta:mainfrom
Conversation
Docker binaries are being used in a similar way as CI binaries, so they should receive the same treatment. While we're at it, add line breaks. See: sourcemeta#304 Signed-off-by: Ratchanan Srirattanamet <peathot@hotmail.com>
peat-psuwit
force-pushed
the
docker-portable
branch
from
40cfc49 to
f57033a
Compare
jviotti
approved these changes
Oct 30, 2025
Member
jviotti
left a comment
jviotti
left a comment
There was a problem hiding this comment.
Ahh great catch. Thank you very much! I will likely release a new version tomorrow
Member
|
Landed in https://github.com/sourcemeta/jsonschema/releases/tag/v12.1.1. The new Docker image will get published soon |
tmeijn
pushed a commit
to tmeijn/dotfiles
that referenced
this pull request
Nov 3, 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 | `v11.11.1` -> `v12.2.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> ### [`v12.2.0`](https://github.com/sourcemeta/jsonschema/releases/tag/v12.2.0) [Compare Source](sourcemeta/jsonschema@v12.1.1...v12.2.0) #### What's Changed - Emit line/column information for YAML schemas and instances by [@​jviotti](https://github.com/jviotti) in [#​529](sourcemeta/jsonschema#529) **Full Changelog**: <sourcemeta/jsonschema@v12.1.1...v12.2.0> ### [`v12.1.1`](https://github.com/sourcemeta/jsonschema/releases/tag/v12.1.1) [Compare Source](sourcemeta/jsonschema@v12.1.0...v12.1.1) #### What's Changed - Disable SIMD support on Docker binaries by [@​peat-psuwit](https://github.com/peat-psuwit) in [#​526](sourcemeta/jsonschema#526) - Get full ECMA 262 regex compliance, Unicode support, and higher performance by [@​jviotti](https://github.com/jviotti) in [#​527](sourcemeta/jsonschema#527) #### New Contributors - [@​peat-psuwit](https://github.com/peat-psuwit) made their first contribution in [#​526](sourcemeta/jsonschema#526) **Full Changelog**: <sourcemeta/jsonschema@v12.1.0...v12.1.1> ### [`v12.1.0`](https://github.com/sourcemeta/jsonschema/releases/tag/v12.1.0) [Compare Source](sourcemeta/jsonschema@v12.0.0...v12.1.0) #### What's Changed - Support printing errors as JSON given `--json` by [@​jviotti](https://github.com/jviotti) in [#​524](sourcemeta/jsonschema#524) - Upgrade Hydra to `38206da873311f0d1fc5f851a9c38838459e89b9` by [@​jviotti](https://github.com/jviotti) in [#​525](sourcemeta/jsonschema#525) **Full Changelog**: <sourcemeta/jsonschema@v12.0.0...v12.1.0> ### [`v12.0.0`](https://github.com/sourcemeta/jsonschema/releases/tag/v12.0.0) [Compare Source](sourcemeta/jsonschema@v11.11.1...v12.0.0) #### What's Changed - Speed up Blaze compilation and fix an infinite loop on circular `$ref`s by [@​jviotti](https://github.com/jviotti) in [#​502](sourcemeta/jsonschema#502) - Fix `jsonschema.json` not being located for relative path inputs by [@​jviotti](https://github.com/jviotti) in [#​504](sourcemeta/jsonschema#504) - Fix `validate` not ignoring top-level keywords sibling to `$ref` by [@​jviotti](https://github.com/jviotti) in [#​505](sourcemeta/jsonschema#505) - Normalise error message metadata by [@​jviotti](https://github.com/jviotti) in [#​520](sourcemeta/jsonschema#520) - Improve schema formatting with `fmt` by becoming dialect aware by [@​jviotti](https://github.com/jviotti) in [#​522](sourcemeta/jsonschema#522) - With this change, `fmt` needs to be able to access custom meta-schemas, so you might need to use `--resolve` or `jsonschema.json` accordingly **Full Changelog**: <sourcemeta/jsonschema@v11.11.1...v12.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:eyJjcmVhdGVkSW5WZXIiOiI0MS4xNTkuNCIsInVwZGF0ZWRJblZlciI6IjQxLjE2Ny4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJSZW5vdmF0ZSBCb3QiXX0=-->
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docker binaries are being used in a similar way as CI binaries, so they should receive the same treatment.
While we're at it, add line breaks.
See: #304