Hi Everyone!
Shortly after release of Panopoly 1.12, a bug in the update process was discovered by Steve Hanson:
https://www.drupal.org/node/2357515
Great catch, Steve! Thanks for reporting the issue right away and including so much detail. :-)
This bug doesn't affect all sites - so, if you updated to Panopoly 1.12 and ran update.php or drush updb without any problems, then you don't need to worry about this.
However, since it will affect some sites and updating to Drupal 7.32 (which is in Panopoly 1.12) is so critical, we've decided to release Panopoly 1.13 with the fix!
(BTW, if you haven't updated yet - you should do so immediately! The security vulnerability fixed in Drupal 7.32 is highly critical.)
For more information, please see the full release notes:
https://www.drupal.org/node/2358829
Remember: you have to update the WHOLE profile - not just the individual panopoly_* modules! Otherwise, you'll be missing important module updates/patches, and it isn't guarenteed to work.
For full instructions on how to upgrade, please see the new Upgrading Panopoly guide! (We invite you to help us improve it as well.)
And, of course, you can find links to download, documentation and report problems on the Panopoly project page:
https://drupal.org/project/panopoly
Thanks!