CI: проверить и выполнить миграцию Azure/login с v2 на v3.1.0
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
Research direction
Read the Azure/login v3.1.0 release notes and the related issue #392, then inspect the developer signing job in the workflow files to confirm its trigger conditions and permissions. Check runner/runtime, inputs, OIDC permissions, Azure environment, and cleanup before choosing a full release SHA. Done means the migration is verified without exposing credentials or granting signing rights to untrusted PRs; record any checks that require maintainer credentials or a manual signing run.
Written by the indexing model from the issue text.
Description
Задача
В developer signing job использует Azure/login v2. Актуальный стабильный релиз — v3.1.0. Это major-миграция: обновлять отдельно от setup-dotnet и без изменения модели доверия подписи. Связано с #392.
Критерии приёмки
- Прочитаны migration/release notes между v2 и v3.1.0; проверены runner/runtime, inputs, OIDC/token permissions, окружение Azure и cleanup.
- После подтверждения совместимости закреплён полный SHA выбранного стабильного релиза; credentials и secrets не попадают в логи.
- Проверены условия запуска signing job и least-privilege permissions; недоверенные PR не получают права подписи.
- Если миграция требует недоступных credentials или ручного signing-прогона, результат и оставшиеся действия явно записаны; успешная подпись не заявляется без проверки.
Источники
База и проверка
По итогам аудита 2026-11-06, developer @ 3363f2131619149e6a25c31e08b6a42a5a4accda. Реализация — отдельная ветка от актуального developer; версии повторно сверить перед изменением.
Перед .NET/NuGet/Python загрузить scripts/env.ps1 или env.sh; сохранять BYDLO_SAFE_DEV=1. Только изолированные тесты/fake runner и fake network; UI — исключительно --mock. Реальные движки, туннели, драйверы и обход блокировок автоматически не проверять. Ручная проверка реального подключения остаётся за мейнтейнером.
- Dominant language
- C#
- Stars
- 5
- Forks
- 1
- Avg merge
- 46m
- Merged PRs (30d)
- 179
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from endercodezz/BYDLO
-
bug P1
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
endercodezz/BYDLO#417 ·
Maintainers usually reply within 1 day
-
dependencies go P3
Difficulty 5/5 Over a week Newbie friendliness 20/100
endercodezz/BYDLO#430 ·
Maintainers usually reply within 1 day
-
dependencies P3
Difficulty 4/5 3-5 days Newbie friendliness 48/100
endercodezz/BYDLO#429 ·
Maintainers usually reply within 1 day
-
dependencies github_actions good first issue P3
Difficulty 3/5 1-2 days Newbie friendliness 52/100
endercodezz/BYDLO#427 ·
Maintainers usually reply within 1 day
-
dependencies P3
Difficulty 3/5 1-2 days Newbie friendliness 48/100
endercodezz/BYDLO#426 ·
Maintainers usually reply within 1 day
All issues in endercodezz/BYDLO
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NethermindEth/nethermind#15684 ·
Maintainers usually reply within 1 day
-
area/ai-assistant squad/flyt
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Altinn/altinn-studio#21798 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
arastella625/DAORework#181 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
BEagle1984/silverback#280 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100