7.7 update did NOT update!

Subscribe. I have the same problem.

As long as your site is up and running, it's not critical.
Don't assign it to yourself unless you are actively working on a fix.
'needs review' is for if you've attached a patch to fix the problem.

Same problem here.
drush up
reports
Project drupal was updated successfully. Installed version is now 7.7.

But the site still complains that a security update is available. Visiting update.php makes those messages go away, but all modules still show up as 7.4 versions, not 7.7.

Subscribe. Same issue. Status report shows 7.7, but also shows "Not secure! (version 7.7 available)"
Thanks--
Al

Subscribe. Same issue with 7.7

Subscribe. Same issue, repeatedly upgraded from 7.4 to 7.7 with no effect.

@all:

Please confirm that the core modules' info files are 7.7. The info file should look something like this

name = Content translation
description = Allows content to be translated into different languages.
dependencies[] = locale
package = Core
version = VERSION
core = 7.x
files[] = translation.test

; Information added by drupal.org packaging script on 2011-07-28
version = "7.7"
project = "drupal"
datestamp = "1311813879"

The version information is the important part.

@ddave: Nope, here's what I see:

$ drush up
[...]
$ cat modules/translation/translation.info 
name = Content translation
description = Allows content to be translated into different languages.
dependencies[] = locale
package = Core
version = VERSION
core = 7.x
files[] = translation.test

; Information added by drupal.org packaging script on 2011-06-30
version = "7.4"
project = "drupal"
datestamp = "1309397516"

Ok, that means that the update-process went wrong. If you look at a unzipped version of 7.7 on your desktop you will see that the version information is correct. That means you either:
1) Did not upload the correct files.
2) Did not upload them to the correct location.
3) Uploaded them into the right location but you didn't delete the old stuff first AND didn't overwrite it with the new stuff correctly.

So grab a fresh version of 7.7 and verify it is indeed 7.7 and update your system correctly. ;)

edit: I am not a drush user but perhaps something went wrong there? Either a bug or a user error.

For example: #1196972: Drush pm-update (up) rollbacks changes if fetching updates fails

I am closing this. Either it is a drush error or a user problem not following the update instructions.

Better to call it a "duplicate" than fixed, this is definitely the drush bug you indicated.

Fine with me. Wasn't sure about the other reports.

Thanks. Had a incomplete copy of 7.7. All good now.