Skip to content

Conversation

@w666
Copy link
Collaborator

@w666 w666 commented Jan 1, 2026

Close #1323

@w666 w666 force-pushed the feature-disable-sha-1 branch from adf3892 to 721387c Compare January 1, 2026 23:06
@smokhov
Copy link
Contributor

smokhov commented Jan 1, 2026

JFOI: it (the SSL test) still breaks without it on AlmaLinux 9, but I can workaround it by setting the var myself before running npm cover

@w666
Copy link
Collaborator Author

w666 commented Jan 1, 2026

Ah, okay. It is fine with me to keep it.

I just investigated a bit and ubuntu 24 has this disabled as well and github actions has been migrated to ubuntu 24, so I assumed it should work in other distros too.

@smokhov
Copy link
Contributor

smokhov commented Jan 1, 2026

Ah, okay. It is fine with me to keep it.

I just investigated a bit and ubuntu 24 has this disabled as well and github actions has been migrated to ubuntu 24, so I assumed it should work in other distros too.

I think it's still OK to proceed with the removal as you indicated.

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.

investigate the need of OPENSSL_ENABLE_SHA1_SIGNATURES=1 in npm cover and npm test

4 participants