How do you manage common release artefacts across multiple production orgs?

One source, many consumers, independent schedules. I extract the shared components — integration frameworks, audit logging, common utilities — into versioned packages built from a single shared repository, and each org installs and upgrades on its own release calendar.

That solves the problem the alternative creates. Copying from a nominated master org is manual and unversioned, so within two changes nobody can say which org has which version, and the four copies diverge into four different products with the same name.

Two governance additions make it stick. A named owner for the shared packages, with a defined intake route for change requests from the consuming orgs. And a supported version skew policy — how far behind an org may fall before it must upgrade — because without it you end up maintaining every historical version simultaneously, which is the divergence you started with.

I would also be honest about what this does not solve. Shared packages do not resolve genuine requirement conflicts between orgs; they surface them earlier, which is better but not free.