Skip to content

Conversation

@askpt
Copy link
Member

@askpt askpt commented Apr 14, 2025

This PR

This pull request includes updates to the Directory.Packages.props file to centralize and manage package versions more effectively, particularly for Microsoft Extensions packages.

Key changes include:

  • Added a new property MicrosoftExtensionsVersion with a default value of 8.0.0 and a conditional value of 9.0.0 for net9.0 target framework.
  • Updated PackageVersion elements to use the new MicrosoftExtensionsVersion property instead of hardcoded version numbers.

Related Issues

Fixes #424

Notes

I tried to follow the https://github.com/App-vNext/Polly approach to determining the dependencies we should bring in. It seems that all the major libraries depend on the lowest version of the target framework.
For example, if the target is net 8.0, the package will be 8.0.0. If the target is net 9.0, the package will be 9.0.0.
Thanks, @kylejuliandev, for the discussion and the examples in Slack.

@askpt askpt linked an issue Apr 14, 2025 that may be closed by this pull request
@codecov
Copy link

codecov bot commented Apr 14, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.71%. Comparing base (65615d8) to head (20e709c).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #426   +/-   ##
=======================================
  Coverage   85.71%   85.71%           
=======================================
  Files          39       39           
  Lines        1603     1603           
  Branches      171      171           
=======================================
  Hits         1374     1374           
  Misses        191      191           
  Partials       38       38           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@askpt askpt marked this pull request as ready for review April 14, 2025 15:19
@askpt askpt requested a review from a team as a code owner April 14, 2025 15:19
Copy link

@weyert weyert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@askpt askpt enabled auto-merge April 14, 2025 16:00
@askpt askpt added this pull request to the merge queue Apr 14, 2025
Merged via the queue into main with commit 3c7dca3 Apr 14, 2025
15 checks passed
@askpt askpt deleted the askpt/424-bug-change-dependency-assets branch April 15, 2025 15:52
github-merge-queue bot pushed a commit that referenced this pull request Apr 24, 2025
Signed-off-by: André Silva <[email protected]>

<!-- Please use this template for your pull request. -->
<!-- Please use the sections that you need and delete other sections -->

## This PR
<!-- add the description of the PR here -->

This pull request updates the Renovate configuration to enhance
dependency management workflows. The most notable changes include
enabling dependency dashboard approval and specifying that dependencies
should not be recreated automatically.

Changes to Renovate configuration:

*
[`renovate.json`](diffhunk://#diff-7b5c8955fc544a11b4b74eddb4115f9cc51c9cf162dbffa60d37eeed82a55a57L5-R7):
Enabled the `dependencyDashboardApproval` setting to require manual
approval for dependency updates.
*
[`renovate.json`](diffhunk://#diff-7b5c8955fc544a11b4b74eddb4115f9cc51c9cf162dbffa60d37eeed82a55a57L5-R7):
Added the `recreateWhen` setting with a value of `"never"` to prevent
automatic recreation of dependency updates.

### Related Issues
<!-- add here the GitHub issue that this PR resolves if applicable -->

Fixes #448

### Notes
<!-- any additional notes for this PR -->
I followed Renovate's general recommendation. I also changed to require
dashboard manual approval because we don't want the PRs to pop up for
dotnet extensions (they should be closed since we need to publish the
lowest version compatible; see #426). So we should look into the
dashboard issue #92 to create the PRs for dependencies.

Signed-off-by: André Silva <[email protected]>
WeihanLi pushed a commit to WeihanLi/openfeature-dotnet-sdk that referenced this pull request May 14, 2025
<!-- Please use this template for your pull request. -->
<!-- Please use the sections that you need and delete other sections -->

## This PR
<!-- add the description of the PR here -->

This pull request includes updates to the `Directory.Packages.props`
file to centralize and manage package versions more effectively,
particularly for Microsoft Extensions packages.

Key changes include:

* Added a new property `MicrosoftExtensionsVersion` with a default value
of `8.0.0` and a conditional value of `9.0.0` for `net9.0` target
framework.
* Updated `PackageVersion` elements to use the new
`MicrosoftExtensionsVersion` property instead of hardcoded version
numbers.

### Related Issues
<!-- add here the GitHub issue that this PR resolves if applicable -->

Fixes open-feature#424

### Notes
<!-- any additional notes for this PR -->

I tried to follow the https://github.com/App-vNext/Polly approach to
determining the dependencies we should bring in. It seems that all the
major libraries depend on the lowest version of the target framework.
For example, if the target is net 8.0, the package will be 8.0.0. If the
target is net 9.0, the package will be 9.0.0.
Thanks, @kylejuliandev, for the discussion and the examples in Slack.

---------

Signed-off-by: André Silva <[email protected]>
Signed-off-by: Weihan Li <[email protected]>
WeihanLi pushed a commit to WeihanLi/openfeature-dotnet-sdk that referenced this pull request May 14, 2025
Signed-off-by: André Silva <[email protected]>

<!-- Please use this template for your pull request. -->
<!-- Please use the sections that you need and delete other sections -->

## This PR
<!-- add the description of the PR here -->

This pull request updates the Renovate configuration to enhance
dependency management workflows. The most notable changes include
enabling dependency dashboard approval and specifying that dependencies
should not be recreated automatically.

Changes to Renovate configuration:

*
[`renovate.json`](diffhunk://#diff-7b5c8955fc544a11b4b74eddb4115f9cc51c9cf162dbffa60d37eeed82a55a57L5-R7):
Enabled the `dependencyDashboardApproval` setting to require manual
approval for dependency updates.
*
[`renovate.json`](diffhunk://#diff-7b5c8955fc544a11b4b74eddb4115f9cc51c9cf162dbffa60d37eeed82a55a57L5-R7):
Added the `recreateWhen` setting with a value of `"never"` to prevent
automatic recreation of dependency updates.

### Related Issues
<!-- add here the GitHub issue that this PR resolves if applicable -->

Fixes open-feature#448

### Notes
<!-- any additional notes for this PR -->
I followed Renovate's general recommendation. I also changed to require
dashboard manual approval because we don't want the PRs to pop up for
dotnet extensions (they should be closed since we need to publish the
lowest version compatible; see open-feature#426). So we should look into the
dashboard issue open-feature#92 to create the PRs for dependencies.

Signed-off-by: André Silva <[email protected]>
Signed-off-by: Weihan Li <[email protected]>
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.

[BUG] Change dependency assets

5 participants