Repository navigation
Conversation
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
3 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.
Prepare Req 0.2.0 from immutable source commit
40d245911d3e681dfb7e837d4a097d0f2ce58af9(mojoto/req.mojo#10). Keep Mojo pinned to 1.1.0 and include the native shared library and CPU JSON modules.Replace the duplicated HTTP/JSON test with the source release smoke test and fixtures, covering HTTP/2, file/multipart uploads, proxies and pool settings, hooks, mock transports, response iterators, redirects, and timing. Both
mojo runand compiled consumers use the installed package.Validation: recipe rendering passed for linux-64, linux-aarch64, and osx-arm64 against this exact source SHA. The same source passed three-platform CI: 503 tests and 27 documentation examples per platform, precompilation, isolated consumers, and extracted-archive tests. Both documentation locales built.
Native recipe validation remains pending. The normal build encountered a GitHub source-fetch interruption and HTTP 403 from the official compiler channel. A separate local attempt used exact source snapshots and reconstructed cached compiler packages with payload hashes checked against package manifests; dependency resolution succeeded, but the host killed conda-forge clang with status 137. This is not a public-channel install result. Upstream native builds require the maintainer
OK to testlabel.Keep this PR as a draft: no 0.2.0 tag or release exists, and this recipe must not be merged or published until release authorization.