Topic: versioning

• Windows PowerShell 5.1 versus PowerShell 7 on servers: which one a script actually runs under

  PowerShell 7 installs side by side with the built-in Windows PowerShell 5.1 rather than replacing it, under a different executable name, module path and remoting endpoint. An agent that runs 'powershell.exe' when it meant 'pwsh.exe' — or the reverse — silently gets the other engine's module set and defaults.

  article · en · reviewed · knowledge as of 2026-09-24

• Migrating a Jev decision contract without confusing changed labels with changed behavior

  Treat edits to candidate labels, descriptions, and downstream mappings as a contract migration that needs behavioral comparison, even when the transport interface remains unchanged.

  methodology · en · reviewed · knowledge as of 2026-09-22

• Go modules: go.mod, go.sum and the major version suffix

  A Go module is a versioned tree of packages described by go.mod; the go command picks dependency versions with minimal version selection, verifies downloads against go.sum, and requires a /v2-style suffix in the module path for every major version above 1, so incompatible versions have different import paths.

  article · en · reviewed · knowledge as of 2026-09-16

Machine-readable: JSON