-
Notifications
You must be signed in to change notification settings - Fork 219
Add Dependabot for Automatic Updates
kellyyangsong edited this page Dec 20, 2023
·
1 revision
Dependabot helps manage your dependencies in three different ways:
- Dependabot alerts—inform you about vulnerabilities in the dependencies that you use in your repository.
- Dependabot security updates—automatically raise pull requests to update the dependencies you use that have known security vulnerabilities.
- Dependabot version updates—automatically raise pull requests to keep your dependencies up-to-date.
Dependabot Version Updates are what we will focus on to remain up to date on Identity Web Releases.
- On GitHub.com, navigate to the main page of the repository.
- Under your repository name, click Settings. If you cannot see the "Settings" tab, select the ••• dropdown menu, then click Settings.
- In the "Security" section of the sidebar, click Code security and analysis.
- Under "Code security and analysis", to the right of Dependabot alerts, click Enable for Dependabot version updates.
- On the next page, an editor will be open to add dependabot.yml to the .github folder of your repo. Add the following to the YAML file:
version: 2
updates:
- package-ecosystem: "nuget"
directory: "/"
schedule:
interval: "daily"
allow:
- dependency-name: "Microsoft.Identity*"
labels:
- "dependabot"
- "dependencies"
- Click Commit Changes to add dependabot to your repo. Now Dependabot can automatically raise pull requests to keep Identity Web up-to-date.
- Home
- Why use Microsoft Identity Web?
- Web apps
- Web APIs
- Using certificates
- Minimal support for .NET FW Classic
- Logging
- Azure AD B2C limitations
- Samples
- Web apps
- Web app samples
- Web app template
- Call an API from a web app
- Managing incremental consent and conditional access
- Web app troubleshooting
- Deploy to App Services Linux containers or with proxies
- SameSite cookies
- Hybrid SPA
- Web APIs
- Web API samples
- Web API template
- Call an API from a web API
- Token Decryption
- Web API troubleshooting
- web API protected by ACLs instead of app roles
- gRPC apps
- Azure Functions
- Long running processes in web APIs
- Authorization policies
- Generic API
- Customization
- Logging
- Calling graph with specific scopes/tenant
- Multiple Authentication Schemes
- Utility classes
- Setting FIC+MSI
- Mixing web app and web API
- Deploying to Azure App Services
- Azure AD B2C issuer claim support
- Performance
- specify Microsoft Graph scopes and app-permissions
- Integrate with Azure App Services authentication
- Ajax calls and incremental consent and conditional access
- Back channel proxys
- Client capabilities