Skip to content
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

Supported version update #48

Merged
merged 1 commit into from
Feb 24, 2023
Merged

Supported version update #48

merged 1 commit into from
Feb 24, 2023

Conversation

jaredpar
Copy link
Member

This seems to have gotten out of date.

This seems to have gotten out of date.
@@ -26,7 +26,7 @@ On the other hand, Google maintains a branch that uses cgo and BoringSSL to impl

### Multiple OpenSSL versions supported

The `openssl` package has support for multiple OpenSSL versions, namely 1.0.1, 1.1.0, 1.1.1 and 3.0.2.
The `openssl` package has support for multiple OpenSSL versions, namely 1.0.2, 1.1.0, 1.1.1 and 3.0.2.
Copy link
Member

@dagood dagood Feb 22, 2023

Choose a reason for hiding this comment

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

Hmm... should 3.0.2 be changed to 3.0.1 also, to match what CI tests? @qmuntal

openssl-version-build: [1.0.2, 1.1.0, 1.1.1, 3.0.1]
openssl-version-test: [1.0.2, 1.1.0, 1.1.1, 3.0.1]

(This might also explain the typo--patch versions swapped between these two.)

Copy link
Contributor

Choose a reason for hiding this comment

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

We should support all OpenSSL 3.0 versions at once, in theory the new versioning policy forbides API breakages between patch versions. Having said this, it might be good to test with OpenSSL 3.0.0 and OpenSSL 3.0.8 (the latest at this moment).

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.

3 participants