Feature Request - Option in 2.0+ settings to change from hexadecimal to semantic numbered workflow versioning

Feature Requests
1

The idea is:

To add a user configurable option to set the default workflow versioning system from hexadecimal to semantic numbered.

eg:

Current workflow versioning in hexadecimal: fd1081e1
Alternate semantic numbered workflow versioning system: 3.4.1

My use case:

Right now, it’s good that 2.0+ has enabled firmer workflow publishing and while this is great for capturing change descriptions, the hexadecimal versioning is difficult to follow in numerous situations.

Some Examples:

  • Team Environments: When working in teams, hexadecimal versions makes it incredibly difficult to ensure everyone is discussing the same version of the workflow.
  • Parallel Branches: When working on multiple-parallel workflows it becomes serious issue
  • Incident Response: “Roll back to the last known-good” is a lot slower slower when the only identifier is fd1081e1 vs “Published v3.4.1”. (Especially over voice/Slack.)
  • Review + Approval: reviewers can’t reliably confirm they’re looking at the same thing when the identifier is unmemorable and error-prone to transcribe.
  • Support Tickets: you want a stable reference like “Workflow X @ v3.4.1” in SOPs, not a hash that changes every save/publish.
  • Cross-Environment Sanity: when comparing dev/stage/prod, a sequential label makes it obvious whether environments are aligned.
  • Non-Dev Stakeholders: ops/PMs will never track hex IDs—they will track “v3.4.1 hotfix”.

I think it would be beneficial to add this because:

  • Reduces cognitive load and transcription errors by shifting from recall (“memorize this hash”) to recognition (simple ordered labels). This is literally a core usability heuristic.

  • Creates a standardised way for teams to reference changes. Version numbering is for communication as much as for machines. That’s the whole point of versioning practices.

  • Aligns with how other systems handle “opaque IDs”: Git uses hashes internally, but routinely presents abbreviated identifiers plus human context because raw hashes suck for humans.

  • Improves release/change management discipline by enabling consistent “release tags” (even if purely UI-level).

  • Semantic Versioning is a widely adopted model for communicating change impact.

Any resources to support this?

Preaching to the converted, but:

Are you willing to work on this?

Yes, absolutely happy to test beta solutions.