You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's been raised that the packer_version field should follow a strict format, and not be free-form.
There are plenty of options for this, the most "popular" one nowadays being semver.
From a technical perspective, it would be nice if there is a way to reliably, automatically check if "version x is newer than version y", so you can specify version ranges easily.
Beyond that, I don't hold any strong opinions on this.
Though we probably shouldn't waste a lot of time on this and decide this quickly, this should not become a blocker.
What are your thoughts? Why?
Note: This only applies to packer_version. _created_by_versioncannot be constrained, as it pertains to pre-existing applications that already have their own versioning schemes.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
It's been raised that the
packer_version
field should follow a strict format, and not be free-form.There are plenty of options for this, the most "popular" one nowadays being semver.
From a technical perspective, it would be nice if there is a way to reliably, automatically check if "version x is newer than version y", so you can specify version ranges easily.
Beyond that, I don't hold any strong opinions on this.
Though we probably shouldn't waste a lot of time on this and decide this quickly, this should not become a blocker.
What are your thoughts? Why?
Note: This only applies to
packer_version
._created_by_version
cannot be constrained, as it pertains to pre-existing applications that already have their own versioning schemes.Beta Was this translation helpful? Give feedback.
All reactions