Artur Spatari e70c880612 test(vault): lock the precedence between two imports ...

Review flagged that multi-import collisions were untested. The order the code
implements is the documented one — Infisical: "If two imports carry a secret
with the same name, the value from the bottom-most import wins" — and the
response lists imports in that order, so sequential assignment matches it.

Added a case with two imports defining the same key. Reversing the merge order
in the client fails it, so the test pins the behaviour rather than restating
the implementation.

vault.test.ts: 58 passed.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-10 10:32:09 +03:00

..

api

chore(api): add local Inngest dev server script

2026-09-01 19:11:27 -06:00

dokploy

test(vault): lock the precedence between two imports

2026-09-10 10:32:09 +03:00

monitoring

fix: resolve 6 critical Dependabot alerts

2026-09-03 17:51:40 -04:00

schedules

fix: pass timezone when removing repeatable schedule job

2026-09-01 01:31:59 -06:00