Skip to content
Pantrysnacks

How to release

We maintain GitHub releases at the repository with a name format of printer-service@version-number.

We just follow basic number versioning, meaning if the last version was printer-service@1 then the next version will be printer-service@2.

How to release

Section titled “How to release”
  1. Create an aarch64 build. You can use Docker and run make release that will give you aarch64 binaries in zig-out/bin/.
  2. Create a zip file for those aarch64 binaries and name it as release.zip. The compression must be zip and file name must be release.zip.
  3. Create an MD5 checksum for the release.zip file.
  • Run md5sum release.zip > checksum.txt. This will create a checksum.txt file containing the MD5 checksum.
  1. Create a GitHub release in GitHub with proper naming convention (printer-service@version-number)
  • Add the MD5 hash in the description of the release.
  • Example: MD5 Hash: a4174c7b2bff547d750149f8c15cae7b. You can get this hash from the checksum file.
  • tag name also must be printer-service@version-number.
  1. If you generated a new image (manually or by image-patcher) then rename that image as pantryclub.img.xz and attach it to the release.

NOTE: Only attach image if you have one. If you only want to release the binary update then just attach the release.zip & checksum.txt files, that’s enough so whenever the Raspberry Pi boots it will download the binaries and update the printer service.

pantryclub.img.xz will be used for further development purposes like if you want to release a new image with image-patcher or want to apply some updates manually.