The updater
Track an upstream source, review each proposed update with its file diff and audit change, then apply or dismiss it.
The updater lets you follow an upstream source and change your copy on purpose, never by surprise. The update queue is in Cloud Team and above, and in the Community edition.
How does tracking work?
You bind a repository to an upstream source: a GitHub repository, a git repository, a well-known index or another SKaaS repository. SKaaS checks it for changes. A new upstream state becomes an update proposal, not a release.
What is in a proposal?
A proposal names the release that it starts from and the release that it proposes, and the upstream reference that it came from. It carries a file diff between the two and an audit delta: the findings that the update adds or removes, and the highest severity that it adds. From the proposal you can apply it or dismiss it. Applying publishes the proposed state as a new release. Dismissing leaves your current release as it is, and the proposal keeps the person, the time and the reason that closed it.
How do I stay on a version?
Use channels. Follow stable or latest, pin a hash, or move a channel back to an earlier release. Pinning is a step of the release and channel commands, not an action of a proposal. See Releases and pinning.
Can updates apply by themselves?
Only if you set a policy that says so. A repository can auto-apply a small content change whose audit has no new Medium or higher finding. The decision checks scripts, executable flags, tools, hooks, file count and edited bytes. A patch version does not override those checks. Otherwise every update waits for you in the update queue.
A SKaaS source follows a repository in the same deployment and organization. Public and internal repositories work directly. A private source needs a token grant to skaas-job-reader:<org id>. Following another deployment is not supported.