Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating package version ranges to be inclusive #256

Merged
merged 1 commit into from
Oct 31, 2018
Merged

Conversation

mathewc
Copy link
Member

@mathewc mathewc commented Oct 31, 2018

Preparing to release 2.3.0 packages, but the current 1.0.23 version of the tools isn't inclusive of this version, causing package installation to fail.

<PackageReference Include="Microsoft.Azure.WebJobs" Version="[2.2.0,2.3.0)" />
<PackageReference Include="Microsoft.Azure.WebJobs.Extensions" Version="[2.2.0,2.3.0)" />
<PackageReference Include="Microsoft.Azure.WebJobs.Extensions.Http" Version="[1.1.0,1.2.0)" />
<PackageReference Include="Microsoft.Azure.WebJobs" Version="[2.2.0,2.4.0)" />
Copy link
Member

Choose a reason for hiding this comment

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

Do we want to move the min version to 2.3.0? This will still use 2.2.0 unless user explicitly updates it.

Copy link
Member Author

Choose a reason for hiding this comment

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

I'd be fine with that, but it means that we'd have to first release all the packages, before releasing this package and updating our tools to use this. @fabiocav ? How do you usually manage these release dependencies?

Copy link
Member Author

Choose a reason for hiding this comment

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

I'll leave the range wider at this point - won't cause any problems.

Copy link
Member

Choose a reason for hiding this comment

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

As long as the redirects are good, this won't be an issue. The only issue here would be if customers update the package reference without having the latest CLI.

@mathewc mathewc merged commit 41b9081 into master Oct 31, 2018
@kashimiz kashimiz deleted the update-range branch December 14, 2021 18:56
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.

3 participants