Repository navigation
deps: bump dotnet/sdk from ed034a8 to e1ffd2a - #87
Merged
Merged
Conversation
Bumps dotnet/sdk from `ed034a8` to `e1ffd2a`. --- updated-dependencies: - dependency-name: dotnet/sdk dependency-version: '10.0' dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/docker/dotnet/sdk-e1ffd2a
branch
from
August 31, 2026 18:32
45c5b79 to
5dda33b
Compare
thomas-lg
added a commit
that referenced
this pull request
Aug 31, 2026
Takes over two Dependabot PRs that kept conflicting as main moved (#97, #94) and folds in three fixes that came out of merging the rest of the batch. Action bumps: - actions/setup-node 6.4.0 -> 7.0.0 (both ci.yml jobs) - docker/login-action 3.7.0 -> 4.6.0 (release.yml) Version-comment drift Dependabot leaves behind: upload-sarif shared the v4 SHA with init/analyze but was still labelled v3, and one checkout SHA carried both '# v7' and '# v7.0.1'. TypeScript is now ignored for minor+major. @angular/build 22 declares peer typescript '>=6.0 <6.1', so 7.x fails npm ci with ERESOLVE (#91) -- and so would 6.1. TypeScript here follows Angular, so it should move with an Angular major, not on its own. 6.0.x patches still flow. refresh-lockfiles.ps1 fixes, both found by running it: - It hardcoded the SDK digest, which #87 had already made stale. It now reads the digest out of the Dockerfile, so that drift can't recur. - Windows PowerShell 5.1 wraps native stderr in ErrorRecords, so with ErrorActionPreference=Stop docker's 'Unable to find image ... locally' pull message killed the script on any machine without the image cached -- i.e. on first use, by the people most likely to need it. Natives now run through a helper that relaxes the preference and judges by exit code.
thomas-lg
added a commit
that referenced
this pull request
Aug 31, 2026
Today's backlog clear-out hit the same friction twice: bumps that all edit one file arriving as one PR each, so every merge re-conflicted the rest. - github-actions majors were ungrouped, so setup-node, upload-artifact, cache and login-action came separately and all touched ci.yml/release.yml. #94 and #97 were rebased repeatedly and ended up folded in by hand. - docker base-image digests all edit the Dockerfile: #67/#68, then #87/#88, each pair needing a sequential update-branch + merge. Grouping both collapses those into one PR per ecosystem per week, matching what the nuget entry already does. Also makes actions-minor-patch's implicit patterns: ["*"] explicit, so the two groups read symmetrically.
thomas-lg
added a commit
that referenced
this pull request
Sep 13, 2026
Bumps dotnet/sdk from `ed034a8` to `e1ffd2a`. --- updated-dependencies: - dependency-name: dotnet/sdk dependency-version: '10.0' dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Thomas Le Gougaud <tom.legougaud@gmail.com>
thomas-lg
added a commit
that referenced
this pull request
Sep 13, 2026
Takes over two Dependabot PRs that kept conflicting as main moved (#97, #94) and folds in three fixes that came out of merging the rest of the batch. Action bumps: - actions/setup-node 6.4.0 -> 7.0.0 (both ci.yml jobs) - docker/login-action 3.7.0 -> 4.6.0 (release.yml) Version-comment drift Dependabot leaves behind: upload-sarif shared the v4 SHA with init/analyze but was still labelled v3, and one checkout SHA carried both '# v7' and '# v7.0.1'. TypeScript is now ignored for minor+major. @angular/build 22 declares peer typescript '>=6.0 <6.1', so 7.x fails npm ci with ERESOLVE (#91) -- and so would 6.1. TypeScript here follows Angular, so it should move with an Angular major, not on its own. 6.0.x patches still flow. refresh-lockfiles.ps1 fixes, both found by running it: - It hardcoded the SDK digest, which #87 had already made stale. It now reads the digest out of the Dockerfile, so that drift can't recur. - Windows PowerShell 5.1 wraps native stderr in ErrorRecords, so with ErrorActionPreference=Stop docker's 'Unable to find image ... locally' pull message killed the script on any machine without the image cached -- i.e. on first use, by the people most likely to need it. Natives now run through a helper that relaxes the preference and judges by exit code.
thomas-lg
added a commit
that referenced
this pull request
Sep 13, 2026
Today's backlog clear-out hit the same friction twice: bumps that all edit one file arriving as one PR each, so every merge re-conflicted the rest. - github-actions majors were ungrouped, so setup-node, upload-artifact, cache and login-action came separately and all touched ci.yml/release.yml. #94 and #97 were rebased repeatedly and ended up folded in by hand. - docker base-image digests all edit the Dockerfile: #67/#68, then #87/#88, each pair needing a sequential update-branch + merge. Grouping both collapses those into one PR per ecosystem per week, matching what the nuget entry already does. Also makes actions-minor-patch's implicit patterns: ["*"] explicit, so the two groups read symmetrically.
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.
Warning
Cooldown could not be applied because no publication date was available from the registry.
Bumps dotnet/sdk from
ed034a8toe1ffd2a.