It's debatable whether this question is on topic here, but here is an approach that works in most cases (User has a quality script manager, like Tampermonkey‡, and default settings):
- Host your script somewhere like GitHub, GreasyFork, etc.
- Make sure your script has a proper
- Provide direct install links to the hosted script, rather then listing the full code here.
- Whenever you make a change to your script, increment the
@version and upload the change to the host from step 1.
Recommend that you also add a short
@history line, to the script's metadata block, summarizing the change. EG:
// @version 2.4
// @history 2.4 HTTPS support; add Tampermonkey metadata.
// @history 2.3 Exclude chat.
When you do the above, Tampermonkey (and most script engines) record the install location and periodically scan the location for script changes. If a newer script is found, the user's script is updated (or the user is asked if she wants to update). Although users have full control over these settings and can alter the defaults, few users actually do.
See also: A more detailed description of the update process.
‡ Violentmonkey probably works correctly, but I haven't verified. Greasemonkey also used to be okay, but GM4 broke so many things that this may be busted too.