In a current project I have had to patch the life out of a few modules (node hierarchy, workbench access and a few more). These modules are now absolutely perfect for the project's needs and are very unlikely to break with future updates to core.
That being said, when the app is handed over the clients will have full (user 1) access to the system and will therefore be warned when these modules have available updates. And they will update them, no matter how many times I beg them not to (oh how easy life would be without clients!).
Is there a way (perhaps in the modules'
.info files) to persuade the update manager not to check for updates for these modules?
I'm aware of the
project status url key that's available for the
.info file so I guess I could set that to a non-existent URL but I'd much rather do this in a clean way if possible.