Hi!
In pybop-team/PyBOP#879, I've been trying to set up some nightly test reporting infrastructure, but our GitHub Actions security requirements are stringent and require all actions to be pinned. The latest release at the time of writing, v1.4.0, does not include #62, and we can't use it because it used an unpinned actions/github-script@v7 back then:
|
uses: actions/github-script@v7 |
Could a new release with the changes from #62 included be cut by the maintainers, whenever it is feasible? I would prefer to use a tagged version/release instead of the main branch, but it's fine as a workaround.
Thank you for your time! 🙏🏻
Hi!
In pybop-team/PyBOP#879, I've been trying to set up some nightly test reporting infrastructure, but our GitHub Actions security requirements are stringent and require all actions to be pinned. The latest release at the time of writing, v1.4.0, does not include #62, and we can't use it because it used an unpinned
actions/github-script@v7back then:issue-from-pytest-log-action/action.yaml
Line 49 in 558a3df
Could a new release with the changes from #62 included be cut by the maintainers, whenever it is feasible? I would prefer to use a tagged version/release instead of the
mainbranch, but it's fine as a workaround.Thank you for your time! 🙏🏻