You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The steps above will create a repository under your own account.
@@ -51,7 +51,7 @@ Plugin packages **must** be digitally signed to be installable in Caido.
51
51
To sign your plugin package, you need to generate a public/private key-pair.
52
52
53
53
::: info
54
-
Plugin package signing is done using [Ed25519 public-key signatures](https://cendyne.dev/posts/2022-03-06-ed25519-signatures.html).
54
+
Plugin package signing is done using [Ed25519 public-key signatures](https://cendyne.dev/posts/2022-03-06-ed25519-signatures.html).
55
55
:::
56
56
57
57
### Generate the Private Key
@@ -99,9 +99,10 @@ The file `public.pem` will contain the following format:
99
99
Now that your repository and key-pair are ready, it’s time to create a release!
100
100
101
101
1.[Create a Github Action Secret](https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions#creating-secrets-for-a-repository) called `PRIVATE_KEY` with the content of the private key generated in [step 3](#3-generate-a-key-pair).
102
+
1.[Enable release immutability](https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/immutable-releases) in the repository General settings.
102
103
1. Go to the `Actions` tab of your repository and trigger the `Release` workflow.
103
104
104
-
This will create a release with the version specified in your project's [caido.config.ts](/guides/config#version) file.
105
+
This will create an immutable release with the version specified in your project's [caido.config.ts](/guides/config#version) file.
0 commit comments