Mac Beta reverted itself to Production channel and won’t change back

I had the same experience, I suppose that there is no new Beta version newer than the Production version
It is still set to Beta in my Preferences/Settings

@Tezcatlipoca

@Gilles Is correct.

When a newer Production build is released you'll move to it from the beta. Because it is the newest at the time and contains all the fixes from the beta cycle. Once a new beta is released you will update to it according to your settings.

If one is not offered then there is not a newer beta available.

Thanks both :)

Does that mean Passkey support is now in Production?

@Tezcatlipoca

Not just yet. :)

Saving and using passkeys is still in beta, and you'll need both the beta of the main 1Password app and the 1Password browser extension to try it out.

☞ Use 1Password beta releases

Huh, I yesterday removed the 1Password (Nightly) App and installed 1Password Beta, which automatically updated to 1Password Production. I can still log in to services using passkeys (stored in 1Password).

The nightly would continue to be installed once you accept a nightly build. This would be true if 30 seconds later you switch to beta or production. Once on anything other than production you will remain on that build type until the next cycle change. Aka a newer Production is released.

I'm not saying you've not encountered a bug but that's how it's supposed to work.

We do not support moving between versions mid cycle. To do this you would need to take steps manually.

Can you explain what "cycle change" means?

• If you create a new Beta, does that always have a version number equal to (or higher than) the current Nightly?
• If not, will you downgrade the 1Password App for people that selected Beta, but are still getting Nightly updates because of their previous channel choice?

You would only change builds when passing a production state. A cycle change would be basically a production build has been released that is newer that the previous beta or nightly builds.

ex.

Update to nightly > Switch to beta> You'll continue to get nightlies > Next cycle change (Production build released) > if your settings are set to Production you only receive the next Production build. If you set your settings (back in step 2) to Beta you should receive the next Beta when one is available. You'll continue to receive Betas. If your settings remained on Nightly in step 2 you'll receive the next available Nightly when available. You'll continue to receive Nightlies.

--

Think of it as a toll road or rail system. Once you get in the carpool lane/ on the tracks you can't exit till the designated area. That would be while the next Production build is on your device. I always recommend setting your desired channel before the next release to ensure you do not miss the lane change area. Else you may need to continue on the ride again.

It is possible to make the change manually should you wish or need to do so. There are a few steps to take if you want to get off the train before the next train station.

Can you please give direct answers to my two questions to help me understand?

I can not follow the logic.
If I change the setting from NIGHTLY to BETA, the consistent behaviour of 1P would be that the next new beta (with a higher build number than the (locally) running "old" NIGHTLY) would be installed. This change should not happen after the "end of the build cycle for a new production version".

Maybe this is not implemented that way, but then the implementation is inconsistent with the settings that are possible/allowed.
Reasoning: If I set the Release channel to BETA, it must be BETA that is installed and not NIGHTLY.
(In addition: When I follow the Help => What's New button (with the small red dot), I end up on the BETA update website.)