Skip to content
This repository was archived by the owner on Jan 12, 2024. It is now read-only.

Conversation

@bamarsha
Copy link
Contributor

@bamarsha bamarsha commented Apr 7, 2021

Use global.json to specify the package version of Microsoft.Quantum.Sdk in one place.

The only other place this version number appears is in the dependency on Microsoft.Quantum.Compiler in the CSharpGeneration project. I'm not sure there is a good way to unify these two, but I suspect those package versions don't need to be in sync with each other in the same way that the SDK version numbers need to, so this could be good enough to close #530.

@cgranade
Copy link
Contributor

cgranade commented Apr 7, 2021

That's a really neat way to use global.json (and indeed, speaks well to the value of making Microsoft.Quantum.Sdk an SDK-style package)! I'd be interested in duplicating this on the libraries repo as well (samples less so, since users will copy and paste each sample such that it's good if samples work without needing repo-wide config files — as noted with @swernli there are exceptions to that, but those exceptions should be carefully considered).

Copy link
Contributor

@cgranade cgranade left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving as it looks good to me, but may want a second opinion from someone closer to runtime.

@bamarsha bamarsha enabled auto-merge (squash) April 7, 2021 21:46
@bamarsha bamarsha merged commit ac0b0e6 into main Apr 7, 2021
@bamarsha bamarsha deleted the samarsha/global-sdk-version branch April 7, 2021 23:01
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

We need a better way to update the package versions across the repo

4 participants