refactor: updated actions/github-script

[mfranzke]

Proposed changes

Resolves #2375

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Refactoring (fix on existing components or architectural decisions)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Further comments

[github-actions]

🔭🐙🐈 Test this branch here: https://db-ui.github.io/mono/review/2375-chore-updated-actionsgithub-script

[mfranzke]

@nmerget there are two new features based on the changelog – as you're much more aware of the pipeline implementation, is there something that we need to further change on this PR?

[nmerget]

@nmerget there are two new features based on the changelog – as you're much more aware of the pipeline implementation, is there something that we need to further change on this PR?

It's fine, the changes won't affect us besides node20

[mfranzke]

@nmerget there are two new features based on the changelog – as you're much more aware of the pipeline implementation, is there something that we need to further change on this PR?

It's fine, the changes won't affect us besides node20

@nmerget okay, in other words, would we profit somehow by adapting our code to these new features, or wouldn't they be of any need for us?

[nmerget]

@nmerget there are two new features based on the changelog – as you're much more aware of the pipeline implementation, is there something that we need to further change on this PR?

It's fine, the changes won't affect us besides node20

@nmerget okay, in other words, would we profit somehow by adapting our code to these new features, or wouldn't they be of any need for us?

We don't have the need, if the pipeline runs it's okay. We can check in the future if we can improve it somehow

[mfranzke]

@nmerget there are two new features based on the changelog – as you're much more aware of the pipeline implementation, is there something that we need to further change on this PR?

It's fine, the changes won't affect us besides node20

@nmerget okay, in other words, would we profit somehow by adapting our code to these new features, or wouldn't they be of any need for us?

We don't have the need, if the pipeline runs it's okay. We can check in the future if we can improve it somehow

why not today? what would be (another) trigger in the future ?

[nmerget]

@nmerget there are two new features based on the changelog – as you're much more aware of the pipeline implementation, is there something that we need to further change on this PR?

It's fine, the changes won't affect us besides node20

@nmerget okay, in other words, would we profit somehow by adapting our code to these new features, or wouldn't they be of any need for us?

We don't have the need, if the pipeline runs it's okay. We can check in the future if we can improve it somehow

why not today? what would be (another) trigger in the future ?

Because we want to release a beta version? If you have time for it, do it ;)

[mfranzke]

@nmerget there are two new features based on the changelog – as you're much more aware of the pipeline implementation, is there something that we need to further change on this PR?

It's fine, the changes won't affect us besides node20

@nmerget okay, in other words, would we profit somehow by adapting our code to these new features, or wouldn't they be of any need for us?

We don't have the need, if the pipeline runs it's okay. We can check in the future if we can improve it somehow

why not today? what would be (another) trigger in the future ?

Because we want to release a beta version? If you have time for it, do it ;)

I've moved the target for this update to the next release after Beta.