v0.5.1

Fix

Social resource nodes could silently send the wrong HTTP request (a DELETE
to a scheduled-posts endpoint instead of the intended publish POST) when
the node instance had no explicit socialOperation saved in its workflow
JSON — n8n does not always persist a value that already equals a field's
schema default. This surfaced as an opaque "Method not allowed" 405 error
with no indication of the actual cause.

• socialOperation now falls back to 'publish' (its own schema default)
  when missing, instead of resolving to undefined.
• getSocialRoute() now throws a clear error for any unrecognized
  operation instead of silently falling through to a DELETE request.

If you hit "Method not allowed" on a Social node, update to this version.