Checked the changes and they're all innocuous. This should hopefully
fix the "externally managed" pip error in these jobs that started
recently.
(cherry picked from commit
dbca3d078ec581600600abebbb18769d3d713914)
- uses: actions/checkout@v4.1.6
- name: Test in FreeBSD
id: test
- uses: vmactions/FreeBSD-vm@f8be330398166d1eb0601f01353839d4052367b2 #v1.0.7
+ uses: vmactions/FreeBSD-vm@d7b8fcc7711aa41ad45e8d9b737cf90f035a7e3d #v1.1.3
with:
usesh: true
prepare: |
- uses: actions/checkout@v4.1.6
- name: Test in NetBSD
id: test
- uses: vmactions/NetBSD-vm@da9ed4d7cd0fb64f330e2342ac5c77ba529b6a11 #v1.0.7
+ uses: vmactions/NetBSD-vm@dd0161ecbb6386e562fd098acf367633501487a4 #v1.1.3
with:
usesh: true
prepare: |
- uses: actions/checkout@v4.1.6
- name: Test in OpenBSD
id: test
- uses: vmactions/OpenBSD-vm@eaa3d3f695a5a52971c23958f6dd4cd3397f959d #v1.0.8
+ uses: vmactions/OpenBSD-vm@ebafa4eac4adf5e7d04e5bbb4aa764b75dd160df #v1.1.2
with:
usesh: true
prepare: |
- uses: actions/checkout@v4.1.6
- name: Test in Solaris
id: test
- uses: vmactions/solaris-vm@548f790d1bc2b9342a76cbb47ddbb85875605559 #v1.0.2
+ uses: vmactions/solaris-vm@960d7483ffd6ac03397964cf6423a2f41332c9c8 #v1.0.9
with:
usesh: true
prepare: |