How do I update the source code ZIP archive when I release a new version?

[pdpolly]

Select Topic Area

Question

Body

I use version releasing on GitHub for add-in packages I produce for use with Mathematica (e.g. https://github.com/pdpolly/Phylogenetics-for-Mathematica). I have been releasing new versions by adding "binaries" associated with a new release tag (e.g. https://github.com/pdpolly/Phylogenetics-for-Mathematica/releases/tag/v.7.0). My package consists of a text file of Mathematica code (*.m) and a PDF user manual, so the files are not genuinely "binaries" or "source code" in the usual meaning of those terms. Everything works like I expect, except the "source code.zip" and "source code.zip.tar" files do not seem to update with my release.

How do I either replace the source files or force them update with the new release? The first time I released the package, the source code contained all the files in my archive, including the PDF and the code file in addition to the READ ME.md, license, and icon. Now the source files seem to contain only the files that were in the main archive prior to the new release. GITHUB docs suggest that they will automatically update when there is a download request, but that does not seem to be the case.

[PadroneSF]

I had a similar issue with a new mod release. I was making many modifications, and they didn't show up in the release packages. Trial and error seemed to indicate that once the release is compressed, the only way to get it updated was to remove the release AND the tags associated with it. By doing that, I was able to see the compressed files get updated when I started over from scratch.

YMMV, this is my first experience with doing releases. Up till now I've just contributed PR's to other projects. I may have misinterpreted the results of what I was doing.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬