<!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi Ken, From my understanding you don't need to create a release for Cuis package. The user have too option to fetch the package code matching a given tag: <ul> <li>From the Github tag page of the repository. For each tag, there are options to download Zip or Tar archives of the matching code. <a class="moz-txt-link-freetext" href="https://github.com/Cuis-Smalltalk/SVG/tags">https://github.com/Cuis-Smalltalk/SVG/tags</a></li> <li>From git command line. </li> <ul> <li>git clone --depth 1 -b Cuis7.0 <a class="moz-txt-link-freetext" href="https://github.com/Cuis-Smalltalk/SVG">https://github.com/Cuis-Smalltalk/SVG</a></li> </ul> </ul> Nevertheless, for DrGeo release, I do as you described: I tag the repository, then create a release to which I attached assets as the Linux and Windows bundles, ready to use for the end users. Associating asset is the only reason for me to use release. It is normal you see these 4 commits difference: you commited additional changes after your tagging. Then as you created a release based on this tag you have this difference. It is also happened to me. In that case you have indeed to delete the tag anchored at a commit in the past, then retag at current commit. You also have to delete the legacy tag remotely, and push the new one. <pre class="moz-signature" cols="72">-- GNU Dr. Geo <a class="moz-txt-link-freetext" href="http://gnu.org/s/dr-geo/">http://gnu.org/s/dr-geo/</a> <a class="moz-txt-link-freetext" href="http://gnu-drgeo.blogspot.com/">http://gnu-drgeo.blogspot.com/</a></pre> </body> </html>