Skip to content

fix: proper LICENSE metadata for package #893

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

RobPasMue
Copy link
Member

Currently, the license is not showing up properly for ansys-dpf-post. This is caused by the way in which the license is referred in the pyproject.toml file. It should be done in this way moving forward

@RobPasMue RobPasMue requested review from moe-ad and PProfizi August 13, 2025 07:46
@RobPasMue
Copy link
Member Author

You can see it here: https://github.com/ansys/pyansys/actions/runs/16913194539/job/47920201265?pr=1035#step:2:980

This requires an immediate fix and patch release @moe-ad @PProfizi

Copy link

codecov bot commented Aug 13, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.13%. Comparing base (c9baf6f) to head (20b2cab).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #893   +/-   ##
=======================================
  Coverage   85.13%   85.13%           
=======================================
  Files          52       52           
  Lines        5214     5214           
=======================================
  Hits         4439     4439           
  Misses        775      775           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Contributor

@moe-ad moe-ad left a comment

Choose a reason for hiding this comment

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

Thanks for this @RobPasMue! @PProfizi is currently OOO and I am not certain about the correct procedure for a pydpf-post release.

I can see that releases are performed from branches, so might be as simple as just creating a patch release branch and triggering the ci_release workflow. i could give that a try or maybe we should wait till Paul returns to avoid breaking things.

@RobPasMue
Copy link
Member Author

We can wait for now if you prefer - but please let me know once there is a new release. Thanks @moe-ad

@moe-ad
Copy link
Contributor

moe-ad commented Aug 13, 2025

Noted. Thanks once again @RobPasMue.

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