feat: script to certify all assets - #211
Merged
Merged
Conversation
nikosxenakis
approved these changes
Apr 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Mo assets, mo problem.
Solution
This PR introduces a script that can be executed via the Juno CLI or GitHub Actions to iteratively re-certify all assets in both heap and stable memory.
What's left TODO
While the script should be run manually when something is off, it should also be included in the current release process (with some modifications, or unless the deployment process is changed). While deploying the assets is likely and hopefully fine, the additional step that re-applies the configuration on every deployment will likely fail. If this pattern is required, the command should actually be removed from the actions, and another script should be written, as the Satellite now exposes a new endpoint that applies the configuration without running the certification.
Both the custom certification and the new configuration endpoint are not yet available in the Juno CLI, because there is currently no other client besides this project that requires them.
Changes
@dfinity/agentand@icp-sdk/coreNotes
The script can be run by an administrator as follow locally with the Juno CLI: