<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Go on Vasiliy Vasilyuk</title><link>https://xorcare.ru/en/tags/go/</link><description>Recent content in Go on Vasiliy Vasilyuk</description><generator>Hugo</generator><language>en</language><managingEditor>xorcare@gmail.com (Vasiliy Vasilyuk)</managingEditor><webMaster>xorcare@gmail.com (Vasiliy Vasilyuk)</webMaster><lastBuildDate>Wed, 25 Sep 2024 19:30:00 +0300</lastBuildDate><atom:link href="https://xorcare.ru/en/tags/go/index.xml" rel="self" type="application/rss+xml"/><item><title>Yet another tool for updating dependencies</title><link>https://xorcare.ru/s/d5184/</link><pubDate>Wed, 25 Sep 2024 19:30:00 +0300</pubDate><author>xorcare@gmail.com (Vasiliy Vasilyuk)</author><guid>https://xorcare.ru/s/d5184/</guid><description>Updating dependencies in Go projects can be a tedious and time-consuming process, especially when dealing with multiple repositories. In this article, the author shares the experience of developing the go-mod-bump script, which significantly simplifies this task by automating routine operations and minimizing the risk of errors.</description></item><item><title>Check actuality of go.mod and go.sum</title><link>https://xorcare.ru/s/8dd13/</link><pubDate>Wed, 24 Jan 2024 01:27:06 +0300</pubDate><author>xorcare@gmail.com (Vasiliy Vasilyuk)</author><guid>https://xorcare.ru/s/8dd13/</guid><description>&lt;p>It happens in practice that you have to revise a merge request and see suspicious changes in go.mod
and go.sum, maybe
only one file is changed, and a legitimate question arises, whether these changes are necessary, or
whether it was
accidentally added to a commit, maybe a colleague forgot to add another file to the commit or to
run &lt;code>go mod tidy&lt;/code> after
removing a dependency? Or maybe it was you yourself who added extra changes in previous commits?&lt;/p></description></item></channel></rss>