Thanks again for your help @pfaffman. To summarize my current understanding:
- Our instance was running 3.4.0.beta4-dev, which is not considered a stable release.
- When I updated my configuration to use
version: stable(with the default commented out), I expected that future rebuilds would lock the instance to the stable branch. However, because we were already on a beta version, the update continued forward—resulting in 3.5.0.beta1-dev. - It appears that switching to
version: stableafter having advanced past the stable tag doesn’t trigger a rollback; it just means that if we were at or below stable, it would pin us to stable instead of tracking beta versions.
Is that correct?
Additionally, could you clarify what the recommended process is to ensure that we don’t accidentally follow the beta channel in the future? Specifically:
- Is leaving
version: stableas the active configuration enough to ensure that, when a stable release is available, our rebuilds will lock into it—provided we haven’t already advanced past it when the stable arrives? - Are there any additional steps or cleanup tasks (such as removing or modifying any other configuration elements) that we should perform to avoid inadvertently updating to beta/development versions?
I’m very much wanting to lock into a stable release ASAP, but don’t want to have it jump over this again…