chore: update actions/cached-node-modules GitHub Action

[dreamorosi]

Summary

Changes

Please provide a summary of what's being changed

This PR updates the hash for the actions/cached-node-modules GitHub Actions to use the latest version. This will allow us to continue using the composite action, which now uses a more recent version of actions/cached.

Please add the issue number below, if no issue is present the PR might get blocked and not be reviewed

Issue number: closes #3548

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dreamorosi]

@leandrodamascena - why the do-not-merge label?

[leandrodamascena]

Before merging, I have a question that I don't know the answer to and I probably need to adopt this in Python as well.

I see that you are adding an action from aws-powertools/actions with sha hash, so does this mean that if you update this action in the source repository, dependabot will be able to bump this version here OR this sha if it is from the main branch?

[dreamorosi]

Before merging, I have a question that I don't know the answer to and I probably need to adopt this in Python as well.

I see that you are adding an action from aws-powertools/actions with sha hash, so does this mean that if you update this action in the source repository, dependabot will be able to bump this version here OR this sha if it is from the main branch?

It's a hash from the main branch, making changes to the repo does not change the source of this action, Dependabot won't pick it up even if we make changes because it requires a release hash, which we don't do.

I've changed this action 6mo ago the last time, and I don't expect to change it for a long time.

[dreamorosi]

Integration tests on this branch were passing.

[leandrodamascena]

Before merging, I have a question that I don't know the answer to and I probably need to adopt this in Python as well.

I see that you are adding an action from aws-powertools/actions with sha hash, so does this mean that if you update this action in the source repository, dependabot will be able to bump this version here OR this sha if it is from the main branch?

It's a hash from the main branch, making changes to the repo does not change the source of this action, Dependabot won't pick it up even if we make changes because it requires a release hash, which we don't do.

Thanks for the explanation.

[dreamorosi]

If we add more actions to that repo, which was the point of having it in the first place, we should probably set up actual releases and leverage Dependabot.

The thing I'm unsure about is how to release multiple packages from the same repo, but we can look into it if needed.

[leandrodamascena]

The thing I'm unsure about is how to release multiple packages from the same repo, but we can look into it if needed.

I'm not sure I understand the question. But if you're talking about releasing multiple actions, I think if we just create a tag and GH release it, dependabot will work.