From e281442835db7dce04ebda43f66381fb51235393 Mon Sep 17 00:00:00 2001
From: David Glasser <glasser@meteor.com>
Date: Tue, 18 Nov 2014 14:28:28 -0800
Subject: [PATCH] Fix `meteor update --patch`.

Broken in d90511128b20910 which is in 1.0 but not 0.9.4. So we should
not create any explicitly-marked-as-patch releases against 1.0.
---
 tools/commands-packages.js | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/tools/commands-packages.js b/tools/commands-packages.js
index 0ca9b36710..1562425b6d 100644
--- a/tools/commands-packages.js
+++ b/tools/commands-packages.js
@@ -1707,7 +1707,8 @@ var maybeUpdateRelease = function (options) {
         "You are at the latest patch version.");
       return 0;
     }
-    var patchRecord = catalog.official.getReleaseVersion(r[0], updateTo);
+    var patchRecord = catalog.official.getReleaseVersion(
+      appTrackAndVersion[0], updateTo);
     // It looks like you are not at the latest patch version,
     // technically. But, in practice, we cannot update you to the latest patch
     // version because something went wrong. For example, we can't find the