Skip to content

Conversation

@paragonie-security
Copy link

More info: https://paragonie.com/blog/2024/04/release-sodium-compat-v2-and-future-our-polyfill-libraries

Description

Add a short description of the change. If this is related to an issue, please add a reference to the issue.

CHANGELOG

  • [CHANGED] Describe your change here. Look at CHANGELOG.md to see the format.

"guzzlehttp/guzzle": "^7.2",
"psr/log": "^1.0|^2.0|^3.0",
"paragonie/sodium_compat": "^1.6"
"paragonie/sodium_compat": "^1|^2"
Copy link
Contributor

Choose a reason for hiding this comment

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

shouldn't you keep the existing lowest bound instead of reverting it to 1.0 ?

Copy link
Author

Choose a reason for hiding this comment

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

That's a good point.

Alternatively, ^1.21|^2 might be more appropriate, given the long list of bug fixes since 1.6.0.

@IanSimpson
Copy link
Contributor

Created #391 with suggested changes from @stof

@stale
Copy link

stale bot commented Feb 1, 2025

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you'd like this issue to stay open please leave a comment indicating how this issue is affecting you. Thank you.

@stale stale bot added the wontfix label Feb 1, 2025
@stale stale bot closed this Apr 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants