yeah, this is a place where people take releases from github and build them into binaries.. as such 1) releases are not happening for every code update, only periodically, and 2) then someone has to care enough to build binaries of the latest release.. so you’re hitting two time delays there. Even though the update has been merged into the current repo codebase, a release with that update has not been published yet, and once it is, you will have to wait until someone takes that release and makes a new build with it and publishes that to proxmarkbuilds.org.
your better bet is to learn how to pull down the red hot current code directly from the github repo and compile it yourself… the instructions Pilgrims posted above is what you’d do if you’ve already done this.. however since you’re using proxmarkbuilds then you likely don’t have any actual code to “git pull” to update to the latest or compile once updated.. you have a pre-built binary compiled by someone else and published to proxmarkbuilds. if you want to get gud and L33T then nuke your current proxmark setup and check this guide to set up proxspace .. this is a pseudo-linux environment for windows just to run all the *nix stuff you need to get current code from github (using git clone to get the code, then git pull to update later), compile it into the client and firmware, and flash the firmware you just made to your proxmark hardware.