How we tell you something you asked for shipped

When something you posted or upvoted is released, the post is set to Shipped and you are notified. The message names the version, says in one line what changed, and links the exact release-notes entry.

Why you get exactly one

A post sends one notification, when it ships, and that is the only guaranteed message. Status changes earlier in its life — moving to Planned, or to In progress — deliberately do not notify, because a stream of intermediate updates trains people to ignore the one that matters. Exactly two moves arrive automatically from the engineering tracker — into In progress when work starts, and into Not planned when a ticket is cancelled — and both are configured with upvoter notification off for the same reason. Planned is not one of them; it is set by hand.

Why it is not automatic

Shipped is set by hand, per post, at release time. Publishing a product update does not set it, and neither does merging the code. Merged is not released, and only something you can install counts.

The practical consequence: if a change is released and the post it came from is still not marked Shipped, it was missed. Reply on the post and it will be fixed — this notification is one of the two things never dropped when time is short.

Making sure it reaches you

• Sign in to post or vote. Anonymous posters and voters cannot be notified at all, which is why guest actions are off.
• Keep the address on your portal account current. The shipped notification goes there.
• Product update emails are a different thing, and they are switched off entirely for now. They are not how you hear about your own post.

If it did not solve your problem

Reply on the post and say so. A shipped status is not a closed door — a reply reopens the conversation, and it is more useful to us than a new post that has lost the original context.