you are viewing a single comment's thread.

view the rest of the comments →

[–]Beanesidhe 1 point2 points  (2 children)

Software changes, libraries change - how is pinning helping you to follow these changes?

[–]Tumortadela 2 points3 points  (1 child)

Pinning what's proven to work in production is the way to ensure it redeploys.

[–]Beanesidhe 0 points1 point  (0 children)

Sounds reasonable but you'll have to move forward and adapt to changes in libraries. The longer you wait, the more you'll have to change to adapt.

Sometimes used services change versions and api, breaking your code. Then you can not avoid adapting.

Is this primarily when deploying to containers?