CommunityToolkit / CommunityToolkit/Labs-Windows

Automate Versions of Packages

Open
#133 7 comments 1 reaction 1 assignee Claimed by @michael-hawker View on GitHub
CI/pipeline 🔬 enhancement help wanted
Dominant language
C#
Stars
482
Forks
89
PR merge metrics
No merged PRs in 30d

Description

## Problem Statement

Each experiment's version number is set by the template and never gets incremented. Therefore every time we merge a PR to main, the packages for all experiments are being rebuilt and repushed to overwrite prior packages in our DevOps feed.

## Expected Behavior

We want to incrementally increase the version number of new packages as we create new builds (and only keep a rolling set of packages, this should be pre-configured in DevOps already).

Ideally, we should only update and push packages for merges to main that contain code that has changed for those experiments, but determining that extra level of optimization would require more work.

At minimum though, we should append the build number to packages so we get a unique NuGet package for experiments. Individual experiment owners can increment their library version number as they deem appropriate otherwise beyond that though to help indicate breaking changes.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.