Conversation
c4980f1 to
fa58331
Compare
2c018ae to
504811e
Compare
ee80388 to
1746bb6
Compare
8fd229a to
432c23e
Compare
| DATABASE_URL: mysql://root:root@127.0.0.1:3306/shopware | ||
| steps: | ||
| - name: Cache npm | ||
| uses: actions/cache@v4 |
There was a problem hiding this comment.
| uses: actions/cache@v4 | |
| uses: actions/cache@v5 |
but do we also want to pin all our action versions to sha here?
There was a problem hiding this comment.
i updated to v5
but do we also want to pin all our action versions to sha here?
What is the benefit 😅 ?
There was a problem hiding this comment.
uses: actions/cache@668228422ae6a00e4ad889ee87cd7109ec5666a7 # v5.0.4https://docs.github.com/en/actions/reference/security/secure-use#using-third-party-actions
Pinning an action to a full-length commit SHA is currently the only way to use an action as an immutable release.
@v5 is just a tag: https://github.com/actions/cache/releases/tag/v5
There was a problem hiding this comment.
TIL: There even is a Require actions to be pinned to a full-length commit SHA setting, but I have no idea how that would behave in combination with our reusable workflows.
There was a problem hiding this comment.
good to know 🤝
I pinned them to 5.0.4
There was a problem hiding this comment.
we could try the setting and see what happens 😄
269a766 to
5f7667d
Compare
resolves https://github.com/shopware/shopware-private/issues/214
Changes
nightly.ymlwith slack notificationreactivate-workflows.ymlin case github deactivates workflows cause of inactivity