What will the error look like if someone tries to use policy-version: 1 in a policy file?
Want to make sure it's easy for a user to tell if they are using an old policy version and what the solution would be.
Will we be providing a guide for how to upgrade policy version 1 files to policy version 2? Or do we expect users that are trying to use an older policy file with a new policy VM to downgrade the VM?

Will we be providing a guide for how to upgrade policy version 1 files to policy version 2?

Didn't have that planned but that's a good idea.

Or do we expect users that are trying to use an older policy file with a new policy VM to downgrade the VM?

I suppose that would be the only option, as we don't plan to support multiple policy lang versions. But using an older VM will probably mean using an older everything else as some of the internal interfaces are evolving as well.

Do people have opinions on how we want to manage the version change? I wasn't planning on landing all the v2 features at once, so there will be some awkward middle ground as it gets built. My thought was I'd throw up the flag early so the version has to be updated now as features roll out. We could also do it at the end. Policies are going to break either way once block scoping is fully enabled.

If we really want it to drop all at once, we could target a feature branch. But I'd rather avoid the PR management hassle if I can.

Do people have opinions on how we want to manage the version change? I wasn't planning on landing all the v2 features at once, so there will be some awkward middle ground as it gets built. My thought was I'd throw up the flag early so the version has to be updated now as features roll out. We could also do it at the end. Policies are going to break either way once block scoping is fully enabled.

If we really want it to drop all at once, we could target a feature branch. But I'd rather avoid the PR management hassle if I can.

we're the primary user of policy right now, so the "rip the bandaid off" approach is probably just fine

I guess I'm not sure of the reason to do the version change now if we are going to do breaking changes later within in this version. Well, I guess there's not much difference in breaking v1 or v2...

I guess I'm not sure of the reason to do the version change now if we are going to do breaking changes later within in this version. Well, I guess there's not much difference in breaking v1 or v2...

I figured it was more polite to do this first so people updating aranya-core get an obvious signal rather than a confusing compile error. I don't think it makes much of a difference for people updating continuously, though. They will suffer these changes multiple times regardless.

What will the error look like if someone tries to use policy-version: 1 in a policy file? Want to make sure it's easy for a user to tell if they are using an old policy version and what the solution would be. Will we be providing a guide for how to upgrade policy version 1 files to policy version 2? Or do we expect users that are trying to use an older policy file with a new policy VM to downgrade the VM?

Good points. The current error message is Invalid policy version: 1... I will update it to say what the supported version is.