docs: version 4.1.0 #2048
Closed
docs: version 4.1.0 #2048
Conversation
This file contains 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
ratankaliani
reviewed
Feb 8, 2025
crates/zkvm/lib/src/ecdsa/affine.rs
Outdated
ratankaliani
approved these changes
Feb 8, 2025
| k256 = { git = "https://github.com/sp1-patches/elliptic-curves", tag = "patch-k256-13.4-sp1-4.1.0" } | ||
| ``` | ||
|
|
||
| Note: The curve operations for `k256` are inside of the `ecdsa-core` crate, so you don't need to patch `k256` itself, and just patching `ecdsa-core` is enough. |
There was a problem hiding this comment.
this is confusing, is it just an artefact from the current version? since there wasn't a k256 patch before
|
Closing, as docs are temporally hosted elsewhere. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR versions the docs for 4.1.0.
Previously we had only maintained "versioned docs", but some commits ended up in the old docs, so this commit reenables "next" docs and unifies the diff between the unmaintained docs and the versioned, thankfully small.
I did this by deleting the unmaintained "next docs", and replacing it with the 4.0.0 docs, then I went through the
git diff, and manually unified them.