Skip to content

Add release workflow for PyPI/ghcr.io and automated license checking #1198

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

Merged
merged 2 commits into from
May 20, 2025

Conversation

ml-evs
Copy link
Member

@ml-evs ml-evs commented May 19, 2025

We should start releasing packages to PyPI (primarily to push our deps metadata cleanly) and to a container registry (for easier builds). This PR adds a release workflow that would initiate that process -- this must be tested carefully via release candidates first.

It also adds a liccheck workflow that reports any dependencies we use that follow non-permissive licenses, such as GPL. I think most likely, we need to at least find the licenses for these dependencies, add an extra section to our license file with them, so that we can push a pre-built docker image that contains the full source of these deps.

@ml-evs ml-evs added the build For issues/PRs pertaining to the build or deployment of the package label May 19, 2025
Copy link

codecov bot commented May 19, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.09%. Comparing base (e8b7c5a) to head (4b92c85).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1198   +/-   ##
=======================================
  Coverage   71.09%   71.09%           
=======================================
  Files          65       65           
  Lines        4300     4300           
=======================================
  Hits         3057     3057           
  Misses       1243     1243           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link

cypress bot commented May 19, 2025

datalab    Run #3360

Run Properties:  status check passed Passed #3360  •  git commit 9192ea32e5 ℹ️: Merge 4b92c8536813410332f4e45e3902d73050a11b69 into e8b7c5a7d9a67867ff8d52781906...
Project datalab
Branch Review ml-evs/release-workflow
Run status status check passed Passed #3360
Run duration 07m 56s
Commit git commit 9192ea32e5 ℹ️: Merge 4b92c8536813410332f4e45e3902d73050a11b69 into e8b7c5a7d9a67867ff8d52781906...
Committer Matthew Evans
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 0
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 504
View all changes introduced in this branch ↗︎

@ml-evs ml-evs force-pushed the ml-evs/release-workflow branch from 34e0bb6 to e1afca2 Compare May 19, 2025 20:46
@ml-evs ml-evs added the CI For issues/PRs regarding the continuous integration label May 19, 2025
@ml-evs ml-evs marked this pull request as ready for review May 19, 2025 20:47
@ml-evs ml-evs force-pushed the ml-evs/release-workflow branch from e1afca2 to 783af6a Compare May 19, 2025 20:50
@ml-evs ml-evs force-pushed the ml-evs/release-workflow branch from 783af6a to 4b92c85 Compare May 20, 2025 11:10
@ml-evs ml-evs merged commit 761e4e2 into main May 20, 2025
17 checks passed
@ml-evs ml-evs deleted the ml-evs/release-workflow branch May 20, 2025 13:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build For issues/PRs pertaining to the build or deployment of the package CI For issues/PRs regarding the continuous integration
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant