Then from the Log tab, we select a commit that we want to consider to be the new version, and then we use Search Everywhere, Shift+Shift, type New Tag… and bring up the dialog to name the tag. First, we bring up the Version Control tool window, Alt+9 on Windows/Linux or Option+9 on macOS. Upgrading non-major versions is relatively straightforward. Now, it’s time to do the same for our own code. In our previous posts, we’ve seen how to use dependencies in our code and how to upgrade or downgrade them. Using a dependency with a new major version.Versioning and migrating to a new major version.Visualizing the dependencies of a project.Starting with a new Go Module from scratch.In case you missed the previous posts, here’s a list of articles from the series: In this article, we’ll cover how to version our project and manage the migration to a new major version. ![]() This is the third, and final, article from our series on Go Modules.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |