Iván Ovejero 33991e92d0 fix(core): Fix missing execution ID in webhook-based workflow producing binary data (#7244) ... Story: https://linear.app/n8n/issue/PAY-839 This is a longstanding bug, fixed now so that the S3 backend for binary data can use execution IDs as part of the filename. To reproduce: 1. Set up a workflow with a POST Webhook node that accepts binary data. 2. Activate the workflow and call it sending a binary file, e.g. `curl -X POST -F "file=@/path/to/binary/file/test.jpg" http://localhost:5678/webhook/uuid` 3. Check `~/.n8n/binaryData`. The binary data and metadata files will be missing the execution ID, e.g. `11869055-83c4-4493-876a-9092c4708b9b` instead of `39011869055-83c4-4493-876a-9092c4708b9b`.		2023-09-25 12:30:28 +02:00
..
integration	refactor(core): Generalize binary data manager interface (no-changelog) (#7164)	2023-09-22 17:22:12 +02:00
shared/ExternalSecrets	feat: External Secrets storage for credentials (#6477)	2023-08-25 10:33:46 +02:00
unit	fix(core): Fix missing execution ID in webhook-based workflow producing binary data (#7244)	2023-09-25 12:30:28 +02:00
extend-expect.ts	feat(core): Security audit (#5034)	2023-01-05 13:28:40 +01:00
setup-mocks.ts	fix(core): Do not allow arbitrary path traversal in the credential-translation endpoint (#5522)	2023-02-21 11:21:04 +01:00
setup.ts	ci: Block all external network calls in tests (no-changelog) (#4930)	2022-12-14 15:28:41 +01:00
teardown.ts	ci: Fix test database cleanup (no-changelog) (#6188)	2023-05-05 12:12:37 +02:00