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

Update manifests when rolling back for install after updating from rollback file #37966

Merged

Conversation

Forgind
Copy link
Member

@Forgind Forgind commented Jan 12, 2024

Fixes #37958 for 2xx

Description
Manifest updates were disabled for Install if the user had previously updated --from-rollback-file, as that clearly indicates they wanted to pin to a specific set of versions, but that did not take into consideration if a user wanted to install --from-rollback-file, which similarly indicates they want a specific version but a different specific version. This takes that into account.

Customer Impact
Customers who called dotnet workload update --from-rollback-file <file> then dotnet workload install --from-rollback-file <file> would have the second command not install the desired versions.

Regression?
Yes. The decision to update or not update is made based on the install state file that was only added in 8.0.1xx.

Risk
Low

Tests
Manual test

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Workloads untriaged Request triage from a team member labels Jan 12, 2024
@Forgind Forgind added Servicing-consider and removed untriaged Request triage from a team member labels Jan 12, 2024
@Forgind Forgind added this to the 8.0.2xx milestone Jan 12, 2024
@Forgind Forgind merged commit 64f87af into dotnet:release/8.0.2xx Jan 16, 2024
16 checks passed
@Forgind Forgind deleted the install-manifests-for-rollback-2 branch January 16, 2024 21:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants