Skip to content

Add one more fix to the S3 release

Tomasz Maczukin requested to merge fix-s3-release-yet-again into master

What does this MR do?

Fixes (let's hope finally!) the S3 releasing job.

Why was this MR needed?

Follow-up for !1803 (merged) and !1807 (merged).

Are there points in the code the reviewer needs to double check?

Does this MR meet the acceptance criteria?

  • Documentation created/updated
  • Added tests for this feature/bug
  • In case of conflicts with master - branch was rebased

What are the relevant issue numbers?

Closes #6551 (closed)

Merge request reports