# Gem releasing with Hoe: VERSION environment variable require

**URL:** <https://www.ruby-forum.com/t/gem-releasing-with-hoe-version-environment-variable-require/104325>\
**Category:** Ruby\
**Created:** [May 16, 2007, 8:02pm UTC](https://www.ruby-forum.com/t/gem-releasing-with-hoe-version-environment-variable-require/104325 "2007-05-16T20:02:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vassilis\_R](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/848f3c/32.png) [@Vassilis\_R](https://www.ruby-forum.com/u/Vassilis_R)\
**Post date:** [May 16, 2007, 8:02pm UTC](https://www.ruby-forum.com/t/gem-releasing-with-hoe-version-environment-variable-require/104325/1 "2007-05-16T20:02:02Z")

</div>

I want to upload a gem to rubyforge and I am using Hoe to do it.

When I do rake release it stops with the message

Must supply VERSION=x.y.z

after creating the gem.

Hoe s v1.2.0. Looking into the code I see:

task :release =\> [:clean, :package] do |t|  
v = ENV[“VERSION”] or abort “Must supply VERSION=x.y.z”

How is this supposed to work?  
Cheers,  
V.-

---

<div class="post-metadata">

**Author:** ![Vassilis\_R](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/848f3c/32.png) [@Vassilis\_R](https://www.ruby-forum.com/u/Vassilis_R)\
**Post date:** [May 17, 2007, 12:17pm UTC](https://www.ruby-forum.com/t/gem-releasing-with-hoe-version-environment-variable-require/104325/2 "2007-05-17T12:17:24Z")

</div>

Vassilis R. wrote:

> task :release =\> [:clean, :package] do |t|  
> v = ENV[“VERSION”] or abort “Must supply VERSION=x.y.z”
> 
> How is this supposed to work?  
> Cheers,  
> V.-  
> To answer my own question:  
> rake release VERSION=x.y.z

It should have been easy, since it is well documented in “Building Your  
First  
Gem With Hoe” by Jacob Harris, only that the slides I found on  
[Hoe Talk](http://www.slideshare.net/vishnu/hoe-talk/) have all the interesting  
points (the commands) garbled (like where on the 3rd slide it says gem  
build, the slide has DFGHIJLM). Might be a browser problem (I’m on  
Firefox on Mac) or a codepage problem.

Luckily I found a PDF version on

> **[NimbleCode.com is For Sale | BrandBucket](https://www.brandbucket.com/names/nimblecode?source=ext)**
>
> Buy the domain name NimbleCode.com and launch your business with a premium domain and a high quality logo.

Just for the record.  
V.-