Consider using actions/upload and download artifact actions

[steveoh]

This best practice seems like something we can apply to this action to increase our security posture.

- name: ⬆️ Upload artifacts
        uses: actions/upload-artifact@v4
        with:
          name: build-artifacts
          path: dist
          retention-days: 1

 - name: ⬇️ Download artifacts
        uses: actions/download-artifact@v4
        with:
          name: build-artifacts
          path: dist

[stdavis]

Would we have to split this into two separate actions so that we could use them in separate jobs in our workflows?

[steveoh]

If the token permission can only be done at the job level, then I suppose it would?