Update vendored dependencies#14373
Conversation
| dependencies: | ||
| markd: | ||
| github: icyleaf/markd | ||
| commit: 5e5a75d13bfdc615f04cc7ab166ee279b3b996d3 |
There was a problem hiding this comment.
I'd suggest using commit pinning for security, like for the other dependencies.
There was a problem hiding this comment.
The code is checked into the repository, and the commit pinned in shard.lock.
A version restriction here is just relevant when you run shards update. And at this point there is no technical reason to restrict that. The latest release will do.
There was a problem hiding this comment.
New releases can include breaking changes, so keeping it unrestricted might break the builds after running shards update. Since the code is checked into the repo, that's not a big issue, just noting.
There was a problem hiding this comment.
Yes, but if you don't try, you could never know. If we realize a compatibility issue, we can add an appropriate restriction.
3 participants
Update the vendored-in dependencies to the latest releases:
replyis still missing a release with the latest changes, so we keep the reference to the latest commit in master.Follow-up to #14365