Skip to content

Conversation

SteveL-MSFT
Copy link
Member

PR Summary

Allows specifying semver requirements via the apiVersion property. Uses the https://docs.rs/semver/latest/semver/struct.VersionReq.html syntax, some examples:

  • 1.1
  • 1.1.*
  • *
  • >1.1.2
  • <=1.3.2
  • >1.1.2, <2.0.0
  • ~1.1
  • ^1.1
  • =1.1

Note that if the version requirement doesn't start with a number, then an = operator is prefixed indicating exact version. Also, adapted resource versioning is NOT part of this PR and will come separately since this PR is already big enough.

dsc resource list will now show multiple versions of a resource and dsc resource has a new --version parameter.

PR Context

Fix #543

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support version pinning in a configuration document
1 participant