Repository navigation
deps: Bump Microsoft.CodeAnalysis.CSharp from 4.12.0 to 5.3.0 #164
dependabot[bot]release-policy.yml
on: pull_request
PR target policy
No version bump in feature PR
29s
staging is caught up with main
7s
Version bump (5 fields in sync)
CHANGELOG entry matches new version
Annotations
13 errors
|
staging is caught up with main
Process completed with exit code 1.
|
|
staging is caught up with main
Then rebase this PR on the updated staging. See CONTRIBUTING.md § Back-merge path.
|
|
staging is caught up with main
gh pr create --base staging --head backmerge/<topic>
|
|
staging is caught up with main
git push -u origin backmerge/<topic>
|
|
staging is caught up with main
git merge origin/main
|
|
staging is caught up with main
git checkout -b backmerge/<topic> origin/staging
|
|
staging is caught up with main
Fix: open a back-merge PR first.
|
|
staging is caught up with main
and this PR was branched from a stale staging.
|
|
staging is caught up with main
This usually means a hotfix landed on main and was not back-merged into staging,
|
|
staging is caught up with main
PR head ('dependabot/nuget/src/tools/winui-analyzer/Microsoft.WindowsAppSDK.Analyzers/Microsoft.CodeAnalysis.CSharp-5.3.0') is missing 30 commit(s) from 'main'.
|
|
No version bump in feature PR
Process completed with exit code 1.
|
|
No version bump in feature PR
See CONTRIBUTING.md § 'Things you should NOT do in a feature PR'.
|
|
No version bump in feature PR
portable plugin version changed from '0.3.1' to ''. Versioning is release-only — only the staging → main promotion PR may bump versions.
|