It is a best practice to have immutable releases, as described at https://docs.github.com/en/code-security/concepts/supply-chain-security/immutable-releases
However, dune-release currently produces release thru a series of mutations, first creating the release, then trying to upload the artifact as a new asset to the release. Trying to use a bistro mode of operation on an immutable release results in
[!] Github API error:
Could not retrieve archive download URL from response
Github API returned: "Cannot upload assets to an immutable release."
See the documentation "https://docs.github.com/rest" that might help you resolve this error.
dune-release: [ERROR] Github API error:
Could not retrieve archive download URL from response
Github API returned: "Cannot upload assets to an immutable release."
See the documentation "https://docs.github.com/rest" that might help you resolve this error.
We could support immutable release if we instead gathered all necessary configuration data, and then created the release via a single request to the API.
It is a best practice to have immutable releases, as described at https://docs.github.com/en/code-security/concepts/supply-chain-security/immutable-releases
However, dune-release currently produces release thru a series of mutations, first creating the release, then trying to upload the artifact as a new asset to the release. Trying to use a bistro mode of operation on an immutable release results in
We could support immutable release if we instead gathered all necessary configuration data, and then created the release via a single request to the API.