Update blog post for 🚢-ing public key scopes

pengwynn · pengwynn · commit 6a8de62a2cf9 · 2014-02-24T15:23:51.000-06:00
diff --git a/content/changes/2014-02-24-finer-grained-scopes-for-ssh-keys.md b/content/changes/2014-02-24-finer-grained-scopes-for-ssh-keys.md
@@ -1,14 +1,9 @@
 ---
 kind: change
 title: Finer-grained OAuth scopes for SSH keys
-created_at: 2014-02-10
+created_at: 2014-02-24
 author_name: jasonrudolph
 ---
-
-**TODO: Set the *real* publication date in the YAML frontmatter and in the file name.**
-
----
-
 Today we're announcing some important changes to the way that API consumers manage SSH keys.
 
 ## Finer-grained OAuth scopes
@@ -21,12 +16,16 @@ In our quest to better enable OAuth applications to only request the permissions
 
 ## Upcoming changes to `user` scope
 
-Historically, `user` scope has provided full access to manage a user's SSH keys. Now that we have dedicated scopes for managing a user's SSH keys, we will soon remove those permissions from `user` scope. Starting **(PUBLICATION DATE + 30 DAYS)**, `user` scope will no longer provide access to SSH keys. Applications that need this access should request one of the new scopes described above.
+Historically, `user` scope has provided full access to manage a user's SSH keys. Now that we have dedicated scopes for managing a user's SSH keys, we will soon remove those permissions from `user` scope. Starting **March 24, 2014**, `user` scope will no longer provide access to SSH keys. Applications that need this access should request one of the new scopes described above.
 
 ## Keys are now immutable
 
 To simplify the security audit trail for SSH keys, we're making keys immutable. API consumers can continue to create keys and delete keys as needed, but keys can no longer be changed. To change an existing key, API consumers should delete the existing key and create a new one with the desired attributes. This change applies both to a [user's SSH keys][user-keys] and a [repository's deploy keys][deploy-keys].
 
+## Deleting keys when revoking a token
+
+In addition, starting today, any keys created via an OAuth token will be
+deleted when that token is revoked.
 
 As always, if you have any questions or feedback, [please get in touch][contact].
 
