In reply to User384774.

To my knowledge, the 'production' (which is the equivalent of the 'master' branch at https://github.com/WordPress/gutenberg) isn't automatically built and shared as .zip file to public.
However, you can build it yourself but if you are not familiar with npm, git, and the command line; it'll take you several hours to learn enough basic terminology of git, npm and the command line to do so.

I wrote how I do it and does expect that you have npm and git installed and that you are using linux or mac os x)

I run ubuntu, so I created an alias, which, for your bash/command line,
is a shortcut that when you type the alias in to your command line and press enter, a series of commands or instructions are run altogether, so I don't have to remember all of these further steps, I can just type in 'gbupdate' and about 3-10 minutes later, you have the newest version of gutenberg ready to go.

Here's what my alias looks like:

alias gbupdate='cd $zach && git checkout master && git fetch upstream && git checkout master && git merge upstream/master && npm install && npm run build'

before going further:
If you only have one site (or environment) where you edit your theme, try out with new plugins, etc, I would be careful running this. There's times where the newest version will unintentionally break an existing block(s) or will have changes in the interface without any documentation why (unless you really dig into the code)

If you're ok with this, you'll have two options:
A] Cloning the copy of gutenberg and keeping it in sync

B] Forking your own copy of gutenberg and keeping it in sync

(There are differences between cloning and forking, that is beyond this article at the moment; I have forked my own copy and proceeded that way; your alias will be different if you only clone)

With that in mind, here's my alias:
alias gbupdate='cd ~/vvv/www/zach/public_html/wp-content/plugins/gutenberg && git checkout master && git fetch upstream && git checkout master && git merge upstream/master && npm install && npm run build'

Your command will not be exactly the same as mine but you can base it off of mine...

cd ~/vvv/www/zach/public_html/wp-content/plugins/gutenberg
- this is a shortcut to the folder where I originally cloned and downloaded my fork of gutenberg from github. (Zach is just the nickname that I gave to the site)

git checkout master
- this tells git to go to the master branch which is the leading branch

git fetch upstream
- tells git to get code changes from the upstream (which is the main Gutenberg project https://github.com/WordPress/gutenberg) (if you haven't already, here are directions to add your upstream from github https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork)

git checkout master
- you may not need to run this again, but I do to be on the safe side.

git merge upstream/master
- merges those downloaded changes in your folder

npm install
- this re-installs, updates any dependencies, of which there's a lot, for gutenberg.

npm run build
- this builds the gutenberg code, so after this command is run, you can now use the newest version of gutenberg on your computer.

more on the differences between npm install and npm run buil https://stackoverflow.com/posts/53311374/revisions

To be honest, I wasn't quite sure of the differences until I wrote this up.

Separately, if you want the zip file that you can share it with friends, etc:
npm run package-plugin
This will delete some of the installation things (I'm not exactly sure what; but I know after I run this program, I have to rerun all of the other commands to get back developing again)

Now.... Requiring all of this knowledge - git, npm, and the command line can seem like it's a lot but it's very useful knowledge to have, not just with troubleshooting gutenberg, but for building and using other software projects and libraries that use node and its package manager, npm.

And yes, for those who wanted to test out the newest version of Gutenerg, requiring to know all of this is sort of a barrier for people ;
that's partially the development team decided if you want to test and share feedback, to use the plugin which releases updates, it seems every few weeks https://wordpress.org/plugins/gutenberg/

It's sort of a tradeoff to decide at what point you want to be involved with steering the direction of Gutenberg.