Skip to content

Conversation

@trejjam
Copy link
Member

@trejjam trejjam commented Dec 19, 2025

Summary

This PR completes the Aviationexam.DependencyUpdater configuration by adding missing required fields and the nuget.config file.

Changes

.github/updater.yml

  • ✅ Added registries array in updates section (references the nuget registry)
  • ✅ Added labels field for automatic PR labeling (dependencies, nuget)
  • ✅ Added commit-message configuration (prefix: chore, include: scope)

nuget.config (new file)

  • ✅ Created at repository root with public NuGet.org registry
  • ✅ Registry key "nuget" matches the key in updater.yml
  • ✅ Includes package source mapping for proper package resolution

Why These Changes Are Needed

According to the Aviationexam.DependencyUpdater documentation, the registries array in the updates section is mandatory to reference which registries (defined at root level) should be used for dependency updates.

The nuget.config file must be present in the same directory as the solution file (repository root in this case) for the updater to correctly resolve package sources.

Testing

The configuration can be tested by:

  1. Manually triggering the "Updater: Dependency Updates" workflow from the Actions tab
  2. Waiting for the scheduled run (daily at 8am UTC)

Related

This completes the setup from the previous PR that added the initial dependency updater workflow.

- Add missing registries array to updater.yml updates section
- Add labels field for PR labeling (dependencies, nuget)
- Add commit-message configuration (prefix: chore, include: scope)
- Create nuget.config with public NuGet.org registry

These changes ensure the Aviationexam.DependencyUpdater GitHub Action
works correctly by providing complete configuration as per documentation.
@trejjam trejjam added this pull request to the merge queue Dec 19, 2025
Merged via the queue into main with commit 3100151 Dec 19, 2025
2 checks passed
@trejjam trejjam deleted the feature/fix-dependency-updater-config branch December 19, 2025 22:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants