OTP26 support #8

Closed
feld wants to merge 0 commits from gitlab-mr-iid-6 into master
Owner

This fixes the test failure in Pleroma as the Map.keys/1 ordering is not guaranteed.

This fixes the test failure in Pleroma as the Map.keys/1 ordering is not guaranteed.
Owner

mix.lock shouldn't be committed in libraries as their only version constraints are in mix.exs.

`mix.lock` shouldn't be committed in libraries as their only version constraints are in `mix.exs`.
I'm not sure about that, see https://hexdocs.pm/elixir/main/library-guidelines.html#dependency-handling
Owner

For very active libraries it could make sense to commit it, but for ones updated not even once a year like all our libraries I think it's better to consider the mix.lock as a SBOM that maybe CI could give as an artifact for reproducibility needs, rather than having it committed and end up with something that you'd need to remember to update everytime a modification is done, else it ends up being stuck in an old era which doesn't matches deployments.

For very active libraries it could make sense to commit it, but for ones updated not even once a year like all our libraries I think it's better to consider the `mix.lock` as a SBOM that maybe CI could give as an artifact for reproducibility needs, rather than having it committed and end up with something that you'd need to remember to update everytime a modification is done, else it ends up being stuck in an old era which doesn't matches deployments.

Pull request closed

Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pleroma-elixir-libraries/http_signatures!8
No description provided.