For platform teams
Keep every service on consistent package versions.
A rule per repository group approves safe upgrades, security fixes come first, and every version is proven on canary services before it spreads.
The problem
You look after the shared packages, templates and pipelines that many .NET services use.
Services drift apart
Each service ends up on its own version of the shared packages.
Every vulnerability touches every service
One fix means edit, restore, build, test and commit in each service repository, again and again.
Findings stay open
Services that are not a priority wait, and the findings stay open.
Big upgrades block other work
When it finally happens, upgrading every service at once takes the team away from planned projects.
What you do today
Three common ways to handle it.
Upgrade by hand
Open each service repository, change the version, build and test. One service at a time.
A bot per repository
A dependency bot opens a pull request in each repository. Someone has to review every one of them.
A spreadsheet of versions and your own scripts
You track which service is on which version yourself and keep the scripts working.
What you get
Consistent versions
One version per package across your repository group, so a shared package does not drift apart.
Security fixes first
Upgrade suggestions put security fixes first, and a rule per repository group decides what is approved without a person.
Proven before it spreads
A version is tried on canary services first. It spreads only after build and tests pass.
Runs in your pipeline
stc runs in an Azure DevOps pipeline without a prompt. Your own pipeline decides what happens after a green run.
Fits your setup
Two things platform teams ask about first.
Your private feeds
Your own framework packages from your private feeds are upgraded like any other package. A new version is tried on your first canary repository before the rest.
A ready-made pipeline task
Add the pipeline task to your Azure DevOps pipeline instead of writing the step yourself.
Is this for you?
For
Platform teams that look after shared packages, templates and pipelines for many similar .NET services.
Not for
A single large application, teams that keep all code in one repository, or teams that do not use .NET.
Join the waitlist
Smell That Code is not open to everyone yet. Join the waitlist and we will tell you when you can try it. A free tier lets you try it on your own repositories.