Context Navigation

Changes between Initial Version and Version 1 of Ticket #32101, comment 23

initial	v1
3	3	I'm not familiar with the infrastructure and code that powers the repo, but I'd imagine that the extra header could be injected during the process of zipping the plugin for delivery. There could also be a measure in place to prevent a commit that removes the header.
4	4
	5	With the opt-out style, in a perfect world, we are asking countless people to update all their private plugins with a new header. How much benefit is there with there still being tons of private plugins without the new header. There is some degree of control over what and how many plugins are in the official repository.
	6
5	7	I think I saw someone mention that such a header could interfere with private plugins with a custom upgrade routine. It shouldn't be too much of an issue since that routine will never fire when the plugin is deactivated. I think improving custom update APIs would be a new ticket.