Understand signed packages and staging
Establish trusted artifact identity before candidate code becomes active.
Before you begin
An update offered through the supported workflow.
Use the controls offered by your installed version and account permissions. This guide describes the workflow; it does not grant additional access.
Follow the steps
- Read release and compatibility details.
- Allow verification of signed metadata and package digest.
- Keep current code running while the candidate is separately staged.
- Let activation and health confirmation finish.
- Retain saved errors if verification fails.
Check the result
An eligible verified artifact reaches activation through the normal process.
If something goes wrong
Do not edit packages, accept invalid signatures or replace same-version bytes. Encoding and signing solve different problems.
Prepare useful details for support