Skip to content

Conversation

@sebastienros
Copy link
Contributor

No description provided.

@github-actions
Copy link
Contributor

github-actions bot commented Nov 4, 2025

The following frameworks were updated, pinging maintainers:
aspnetcore: @DamianEdwards, @sebastienros

@sebastienros
Copy link
Contributor Author

@DamianEdwards @LoopedBard3

Copy link
Contributor

@DamianEdwards DamianEdwards left a comment

Choose a reason for hiding this comment

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

Change looks good. This shouldn't be merged until release day (11/11) when the container images become available.

@sebastienros
Copy link
Contributor Author

sebastienros commented Nov 4, 2025

@DamianEdwards
Copy link
Contributor

@sebastienros those 404 for me. What was your point?

@sebastienros
Copy link
Contributor Author

The tag:10 images are available, and I copy pasted the urls ... they use some weird routing framework and the url they generate is not accessible directly ;)

@DamianEdwards
Copy link
Contributor

@sebastienros I see, so they point at the rc.2 version right now?

@msmith-techempower
Copy link
Member

I don't really see why the UPDATES test would be suddenly failing due to these changes, unless there's a built-in ORM that got updated with 10.0.

@sebastienros
Copy link
Contributor Author

@msmith-techempower I actually ran a fake change in master and the same issues are showing up. We will investigate, the two reasons I can think of is that the verification logic changed, or something happened in a service change of DotNet that the docker tag would have pulled automatically.

I checked our implementation, which is not using an advanced orm (no caching or optimizations) and it looks correct. So a mystery so far.

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.

4 participants