Pantheon: Downloading updates failed

Updates to Drupal core aren't supported by Drupal yet. It still doesn't even work w/ Drush. I've documented a 2 different workflows in Upgrading the CiviCRM Starter Kit. Ultimately this processes will be the same as the process used to upgrade Drupal now.

The process is different using the Pantheon Dashboard. Unfortunately since we want the Drupal.org packaging to add the version number to the distribution, there will alway be a short period where Drupal's update status is telling you that a new version of the starter kit is available, but the update isn't showing up on Pantheon.

This notice of an update without the option to update using Pantheon will exist even longer if Drupal.org's packaging is delayed for some reason and I move on to other projects or take a break from staring at my screen. That's what happened with the 4.3.3 update. I tagged the new packaging on Drupal.org on Friday, but just pushed the changes from Drupal to Pantheon yesterday.

I've started some documentation for... Upgrading the CiviCRM Starter Kit on Pantheon

Please feel free to improve that.

@Time has come,

Thanks, but I can't take much of the credit. While I did play a small part in helping to make packaging install profiles on Drupal.org a reality, the really exciting work that makes these updates possible is happening at Pantheon... and of course credit for having reasons to update belongs to the CiviCRM team. I'm just pointing out that the peanut butter and chocolate taste better when you use them together :)

Sorry duplicate see #5

I am having the same issue now when trying to update 7.x-4.4-rc9 to 7.x-4.4-rc11.
However there is no automatic way to update through the Pantheon's dashboard.
Can anyone offer suggestions on getting 7.x-4.4-rc9 to 7.x-4.4-rc11 update on Pantheon.

The update to CiviCRM 4.4.7 and Drupal 7.32 should be showing up on your Pantheon Dashboard shortly. The packaging to the distribution on Drupal.org does not automatically make it available on Pantheon. That requires additional steps of merging https://github.com/pantheon-systems/drops-7 with https://github.com/kreynen/civicrm-starterkit-drops-7. I test the packaged version from Drupal.org before pushing it to Pantheon users if it creates more problems than the update solves, I'll delaying updating until I have more time to test and patch CiviCRM.

Because Pantheon is such a unique environment with its dynamic bindings, updates that work fine in most LAMP stacks often have errors when I test them on Pantheon. We need more people testing that, but get to that point I probably need to write some documentation for how someone would do that.

I've had several offers to help with this distribution, but no one has actually followed through. Pantheon's support staff have gotten increasingly hostile and less helpful with CiviCRM related issues. "The issue is with CiviCRM. Post to CiviCRM.org for help" is a common response. Obviously that isn't going to get you very far since the binding related errors are a very Pantheon specific problem. On any other environment with multiple webservers, you'd simply create a symlink for the binding path and make that consistent across all your servers.

I've started a new branch for the CiviCRM 4.5.x updates, but getting that working will require more work and testing. With the 4.3.x -> 4.4.x, I included a 2nd profile option for a few releases. Users could use https://www.drupal.org/project/profile_switcher to try out the new version of CiviCRM on their dev environment. Not sure if I'll do that again since it was a lot of work and I got very little feedback.

I'll post more about that, but moving this to fixed for now.