Closed RomainOliva closed 1 year ago
My bad it's not the JS compilation, it's from a commit change, I edit the issue
Thank you for reporting the issue, we will take a look ang get back to you.
I have the fix but I don't have the right to push my PR, there is the fix :
const bucketPrefix = bucketPrefixes.join(path.sep).replace(/\$([_a-z]+\w*)|\$\{(\w*)\}/giu, (match, p1, p2) => {
return process.env[p1 || p2] ?? match
})
You have just to escape {
and }
caracters
I have the fix but I don't have the right to push my PR, there is the fix :
const bucketPrefix = bucketPrefixes.join(path.sep).replace(/\$([_a-z]+\w*)|\$\{(\w*)\}/giu, (match, p1, p2) => { return process.env[p1 || p2] ?? match })
You have just to escape
{
and}
caracters
Not sure I follow, are you not able to open a PR or?
If this is tested, we can update it.
Yes i don't have permission :
I test the regex online yes :
it's the same regex but escaped to avoid the js error
Can you just commit the fix and release with the regex escaped please 😇 ?
The PR is created : https://github.com/RimacTechnology/semantic-release-s3/pull/18
:tada: This issue has been resolved in version 2.2.3 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Issues
semantic-release-s3
Version You Are Usingv2.2.2
Your Config
Node: 16 (I tried in 18 it's the same problem) Yarn: 1.22.17
Steps to reproduce
Send a config like this :
Expected behavior
The problem came from this change :
https://github.com/RimacTechnology/semantic-release-s3/commit/e31cc03beccb52330ad313ba9ac1cc4c78d88407#diff-a7a74f2666de0f501942c3e3c0ff9146e86f8fb359f8cf521dcdb205490b0e3eR34
This throw the error below (i try in the chrome console too)
Do you have any idea of the problem ?
Thanks a lot :)
Actual behavior