s2n 1.5.18

[BrewTestBot]

Created by brew bump

---

Created with brew bump-formula-pr.

release notes

Weekly release for April 28 2025
Release summary:

Adds a new security policy (20250414), which fixes a gap in compatibility in 20250211 by extending the allowed signatures to include those on P-256.

What's Changed

chore(ci): revert nix installer pin by @dougch in chore(ci): revert nix installer pin aws/s2n-tls#5251
ci: add awslcfips to nix jobs by @dougch in ci: add awslcfips to nix jobs aws/s2n-tls#5205
chore: add new team member by @anupamym in chore: add new team member aws/s2n-tls#5259
chore: bindings release 0.3.17 by @anupamym in chore: bindings release 0.3.17 aws/s2n-tls#5260
refactor: cleanup hash to better support multiple implementations by @lrstewart in refactor: cleanup hash to better support multiple implementations aws/s2n-tls#5258
tests: add ml-dsa test certs from RFC by @lrstewart in tests: add ml-dsa test certs from RFC aws/s2n-tls#5261
feature: add support for configuring (but not yet using) ml-dsa certs by @lrstewart in feature: add support for configuring (but not yet using) ml-dsa certs aws/s2n-tls#5263
Add 20250414 security policy by @Mark-Simulacrum in Add 20250414 security policy aws/s2n-tls#5253
refactor: remove unused hash methods by @lrstewart in refactor: remove unused hash methods aws/s2n-tls#5269
build(deps): bump JulienKode/team-labeler-action from 1.3.0 to 2.0.0 in /.github/workflows in the all-gha-updates group by @dependabot in build(deps): bump JulienKode/team-labeler-action from 1.3.0 to 2.0.0 in /.github/workflows in the all-gha-updates group aws/s2n-tls#5252
build: add -Wa,-mbranches-within-32B-boundaries compiler flag by @johubertj in build: add -Wa,-mbranches-within-32B-boundaries compiler flag aws/s2n-tls#5267

New Contributors

@anupamym made their first contribution in chore: add new team member aws/s2n-tls#5259

Full Changelog: aws/s2n-tls@v1.5.17...v1.5.18

---

[github-actions]

🤖 An automated task has requested bottles to be published to this PR.

Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch.