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

[main] Update dependencies from dotnet/aspnetcore #6081

Closed

Conversation

dotnet-maestro[bot]
Copy link
Contributor

@dotnet-maestro dotnet-maestro bot commented Apr 13, 2022

This pull request updates the following dependencies

From https://github.com/dotnet/aspnetcore

  • Subscription: f048ef0c-9fda-42a1-fd39-08da1d875c10
  • Build: 20220512.8
  • Date Produced: May 12, 2022 11:58:54 PM UTC
  • Commit: fac970ded3047f63328ff56f59a874bcabf18126
  • Branch: refs/heads/release/6.0

…0220413.4

Microsoft.AspNetCore.Metadata , Microsoft.AspNetCore.Components.WebView , Microsoft.AspNetCore.Components.Web , Microsoft.AspNetCore.Components.Forms , Microsoft.AspNetCore.Components.Analyzers , Microsoft.AspNetCore.Components , Microsoft.AspNetCore.Authorization , Microsoft.JSInterop
 From Version 6.0.4 -> To Version 6.0.5
@ghost ghost added the area/infrastructure 🏗️ CI, Maestro / Coherency label Apr 13, 2022
@TanayParikh TanayParikh requested review from jonathanpeppers and a team April 13, 2022 19:56
@wtgodbe
Copy link
Member

wtgodbe commented Apr 13, 2022

Is there a fabric bot config for this repo? You could get it to auto-approve these PRs

@TanayParikh
Copy link
Contributor

Is there a fabric bot config for this repo? You could get it to auto-approve these PRs

Looking through some recent dep-update PRs, that doesn't seem to be something this repo uses (I just see manual approvals).

@TanayParikh TanayParikh added the do-not-merge Don't merge this PR label Apr 13, 2022
Copy link
Contributor

@TanayParikh TanayParikh left a comment

Choose a reason for hiding this comment

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

Blocking merge as we don't want to upgrade to 6.0.5 yet.

@TanayParikh
Copy link
Contributor

TanayParikh commented Apr 13, 2022

@wtgodbe is there a way to only consume publicly available releases (ie. 6.0.4 for now)? Perhaps via a different channel?

@wtgodbe
Copy link
Member

wtgodbe commented Apr 13, 2022

@wtgodbe is there a way to only consume publicly available releases (ie. 6.0.4 for now)? Perhaps via a different channel?

As far as I know, not automatically. You'd have to disable the subscription, then manually trigger it locally against the specific build that produced 6.0.4 (unless there's some new mechanism for this - @mmitche?)

@mmitche
Copy link
Member

mmitche commented Apr 13, 2022

@wtgodbe is there a way to only consume publicly available releases (ie. 6.0.4 for now)? Perhaps via a different channel?

As far as I know, not automatically. You'd have to disable the subscription, then manually trigger it locally against the specific build that produced 6.0.4 (unless there's some new mechanism for this - @mmitche?)

There's not a mechanism or mechanism planned for this. You can do the update manually though. You find the manifest file for the release, then checkout your main branch and do:

$builds = Get-Content '<manifest file>' | ConvertFrom-Json; $builds.builds | % { if ($_.channels.name -eq ".NET 6 Internal") { darc update-dependencies --id $_.barBuildId } }

This will update against the all runtime repos, though not SDK (you can use another invocation for that), for the given release. The manifest file can be found on vsufile. If you need info on where to look, ping me offline.

…0220413.12

Microsoft.AspNetCore.Metadata , Microsoft.AspNetCore.Components.WebView , Microsoft.AspNetCore.Components.Web , Microsoft.AspNetCore.Components.Forms , Microsoft.AspNetCore.Components.Analyzers , Microsoft.AspNetCore.Components , Microsoft.AspNetCore.Authorization , Microsoft.JSInterop
 From Version 6.0.4 -> To Version 6.0.5
…0220413.12

Microsoft.AspNetCore.Metadata , Microsoft.AspNetCore.Components.WebView , Microsoft.AspNetCore.Components.Web , Microsoft.AspNetCore.Components.Forms , Microsoft.AspNetCore.Components.Analyzers , Microsoft.AspNetCore.Components , Microsoft.AspNetCore.Authorization , Microsoft.JSInterop
 From Version 6.0.4 -> To Version 6.0.5
@dougbu
Copy link
Member

dougbu commented Apr 28, 2022

@mmitche any idea what MAUI-public is or why there's no Details for it❔ Mainly wondering if this PR should be merged by someone who has the right rights…

<Dependency Name="Microsoft.AspNetCore.Authorization" Version="6.0.4">
<Uri>https://dev.azure.com/dnceng/internal/_git/dotnet-aspnetcore</Uri>
<Sha>f9ae0f5d30be2de3c0de61b5673bd8873231d70a</Sha>
<Dependency Name="Microsoft.AspNetCore.Authorization" Version="6.0.5">
Copy link
Member

Choose a reason for hiding this comment

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

Are these packs going to ship the same timeframe as the 6.0.5 dotnet/runtime?

Just checking that these will be on NuGet.org when MAUI ships. /cc @Redth as a reviewer

Copy link
Contributor

Choose a reason for hiding this comment

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

Are these packs going to ship the same timeframe as the 6.0.5 dotnet/runtime?

It was going to be in a very tight timeframe. I think the decision we'd reached was we want to hold off on merging this PR (and thereby upgrading from 6.0.4 -> 6.0.5) till after GA to be safe.

Mainly wondering if this PR should be merged by someone who has the right rights…
@dougbu

No it should NOT be merged. Ideally we'd only consume this package update once the packages are publicly available, but unfortunately, that doesn't seem to be possible. So blocking the PR was the alternative.

Copy link
Member

Choose a reason for hiding this comment

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

@TanayParikh the workflow above will get you what you want, once the build is officially released (week from Tuesday).

Copy link
Member

Choose a reason for hiding this comment

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

Any change here? i.e. is this PR able to be merged?

@mmitche
Copy link
Member

mmitche commented Apr 28, 2022

@dougbu I don't. It doesn't show up as run on any other PRs I checked.

@TanayParikh TanayParikh added the blocked Work that is currently blocked label Apr 28, 2022
@javiercn
Copy link
Member

javiercn commented May 3, 2022

@mkArtakMSFT do you know if this is still blocked for merging?

@TanayParikh
Copy link
Contributor

@mkArtakMSFT do you know if this is still blocked for merging?

It's still blocked. Please see: #6081 (comment)

…0220503.6

Microsoft.AspNetCore.Metadata , Microsoft.AspNetCore.Components.WebView , Microsoft.AspNetCore.Components.Web , Microsoft.AspNetCore.Components.Forms , Microsoft.AspNetCore.Components.Analyzers , Microsoft.AspNetCore.Components , Microsoft.AspNetCore.Authorization , Microsoft.JSInterop
 From Version 6.0.4 -> To Version 6.0.6
…0220504.26

Microsoft.AspNetCore.Metadata , Microsoft.AspNetCore.Components.WebView , Microsoft.AspNetCore.Components.Web , Microsoft.AspNetCore.Components.Forms , Microsoft.AspNetCore.Components.Analyzers , Microsoft.AspNetCore.Components , Microsoft.AspNetCore.Authorization , Microsoft.JSInterop
 From Version 6.0.4 -> To Version 6.0.6
…0220505.18

Microsoft.AspNetCore.Metadata , Microsoft.AspNetCore.Components.WebView , Microsoft.AspNetCore.Components.Web , Microsoft.AspNetCore.Components.Forms , Microsoft.AspNetCore.Components.Analyzers , Microsoft.AspNetCore.Components , Microsoft.AspNetCore.Authorization , Microsoft.JSInterop
 From Version 6.0.4 -> To Version 6.0.6
…0220509.8

Microsoft.AspNetCore.Metadata , Microsoft.AspNetCore.Components.WebView , Microsoft.AspNetCore.Components.Web , Microsoft.AspNetCore.Components.Forms , Microsoft.AspNetCore.Components.Analyzers , Microsoft.AspNetCore.Components , Microsoft.AspNetCore.Authorization , Microsoft.JSInterop
 From Version 6.0.4 -> To Version 6.0.6
…0220510.8

Microsoft.AspNetCore.Metadata , Microsoft.AspNetCore.Components.WebView , Microsoft.AspNetCore.Components.Web , Microsoft.AspNetCore.Components.Forms , Microsoft.AspNetCore.Components.Analyzers , Microsoft.AspNetCore.Authorization , Microsoft.AspNetCore.Components , Microsoft.JSInterop
 From Version 6.0.4 -> To Version 6.0.6
…0220510.8

Microsoft.AspNetCore.Metadata , Microsoft.AspNetCore.Components.WebView , Microsoft.AspNetCore.Components.Web , Microsoft.AspNetCore.Components.Forms , Microsoft.AspNetCore.Components.Analyzers , Microsoft.AspNetCore.Authorization , Microsoft.AspNetCore.Components , Microsoft.JSInterop
 From Version 6.0.4 -> To Version 6.0.6
@rmarinho
Copy link
Member

Should this be merged now ?

@rmarinho
Copy link
Member

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 2 pipeline(s).

@javiercn
Copy link
Member

@rmarinho I think so. 6.0.5 is out, which is what we were waiting for, I believe.

@Redth
Copy link
Member

Redth commented May 12, 2022

this is 6.0.6 though? let's pause on merging please.

@rmarinho rmarinho added do-not-merge Don't merge this PR and removed do-not-merge Don't merge this PR blocked Work that is currently blocked labels May 12, 2022
@rmarinho
Copy link
Member

Oh right i was thinking it was 6.0.5 also. but i see now is 6.0.6

@mmitche
Copy link
Member

mmitche commented May 12, 2022

FYI that 6.0.6 won't ever be the actual 6.0.6 until after release, since 6.0.6 (and 6.0.5 for that matter) are internal only.

@rmarinho
Copy link
Member

@mmitche
Copy link
Member

mmitche commented May 12, 2022

@mmitche 6.0.5 are public no? https://www.nuget.org/packages/Microsoft.AspNetCore.Components.Forms/6.0.5

6.0.5 is public, 6.0.6 is still being built.

@TanayParikh
Copy link
Contributor

Even if we revert this PR to the 6.0.5 bump, I'm hesitant to take this for GA at this stage. I think it may be better we stick to 6.0.4 for now and upgrade to 6.0.5/6 after GA, I don't want to touch anything at this stage of the release.

@TanayParikh TanayParikh added the blocked Work that is currently blocked label May 12, 2022
@rmarinho
Copy link
Member

We have this other #7107 with 6.0.5 that will not be for GA but for servicing. We already branched the GA version

@TanayParikh
Copy link
Contributor

Created #7109 to merge in 6.0.5 to main. Can't merge this PR as it's 6.0.6

…0220512.8

Microsoft.AspNetCore.Metadata , Microsoft.AspNetCore.Components.WebView , Microsoft.AspNetCore.Components.Web , Microsoft.AspNetCore.Components.Forms , Microsoft.AspNetCore.Components.Analyzers , Microsoft.AspNetCore.Authorization , Microsoft.AspNetCore.Components , Microsoft.JSInterop
 From Version 6.0.5 -> To Version 6.0.6
@TanayParikh
Copy link
Contributor

TanayParikh commented Jun 15, 2022

We no longer need this as the dependabot is taking care of this for us #8057. The subscription has also been disabled.

@TanayParikh TanayParikh deleted the darc-main-cae2c232-320e-44a9-887a-919d6df01459 branch June 15, 2022 22:31
@github-actions github-actions bot locked and limited conversation to collaborators Dec 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/infrastructure 🏗️ CI, Maestro / Coherency blocked Work that is currently blocked do-not-merge Don't merge this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants