Repository navigation
chore: pin current database images in the identity sample - #217
Merged
Merged
Conversation
This was referenced Oct 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The sample explicitly selects PostgreSQL 18.4 and pgAdmin 9.18.0 with current image digests instead of relying on older Aspire defaults.
Closes #216
Validation: locked restore, Release build, 444 unit/integration/component tests, 27 real browser E2E tests, CSharpier and direct/transitive NuGet vulnerability checks passed. No tests were skipped.
The pgAdmin 9.18.0 container served its login page in a disposable local smoke test. This sample-only change needs no identity-package release.