A new configuration extra-local-artifacts would make this easier to do this kind of thing (great for adding for example cargo-deb debian packages). The structure would look very similar to extra-artifacts but would obviously run in the local step context.
It would be good to be able to specify whether the additional artifact should live in within the target archive or outside of it. For example, a .deb should not be copied over by archive installers or remain in the install folder, so it should live outside the archive. In this case, the target should be appended to the extra artifact name.
Currently, in order to build extra local artifacts and incorporate them into the release, a user must disable
build-local-artifactsand recreate a GitHub actions artifact with the desired artifacts, as specified here: https://opensource.axo.dev/cargo-dist/book/reference/config.html#build-local-artifactsA new configuration
extra-local-artifactswould make this easier to do this kind of thing (great for adding for examplecargo-debdebian packages). The structure would look very similar toextra-artifactsbut would obviously run in the local step context.It would be good to be able to specify whether the additional artifact should live in within the target archive or outside of it. For example, a
.debshould not be copied over by archive installers or remain in the install folder, so it should live outside the archive. In this case, the target should be appended to the extra artifact name.