Looks cool. Did we discuss using a single sri file vs the 3 you added?
Need to test it locally before merge.

No, we didn't. I just felt the need for separating and categorizing the hashes by component.

I guess it would be easier for tool driven consumption when all hashes are contained in a single file.
(if this is too much work, we can just merge as is)

Make sense. I will update it this evening.

@staabm
Updated per suggestion!

Hi@staabm

any comment on this PR?
Should I add those files to the list ofdistribution files in case we want to commit them to GitHub?

I love this change.

Should I add those files to the list of distribution files

I guess we should.

we want to commit them to GitHub?

we dont have this dist folder in our codebase on github.. I dont get what you mean here?

I would like to see the hash on the website, next to the download link.

we dont have this dist folder in our codebase on github.. I dont get what you mean here?

We publish thedist folder with every tagged release. For example, seehttps://github.com/jquery-validation/jquery-validation/tree/1.17.0
So, if someone navigates the tags, they will see thedist folder with its content (additional-methods.js,additional-methods.min.js,jquery.validate.js,jquery.validate.min.js). And I would like to add the sri file to be added to this list too.

I would like to see the hash on the website, next to the download link.

We can provide a link to the file in our docs. The file will be hosted here on GitHub, so everyone can access it without going to the website.

ok cool. please go for it then.

@staabm

Updated the proposal to include the sri hashes file in tagged releases.

Hi@staabm,

Can we merge this PR? Does it need any other changes I need to do?

Looks great, thanks