License-binary drift detected

[github-actions]

Task Summary

License-binary drift on 7a6c22a (run).

Where:

• build / pyamber (ubuntu-latest, 3.12) — Check installed Python packages against per-module LICENSE-binary files (logs)

How to resolve: refresh the per-module LICENSE-binary file(s) to match the bundled versions.

Task Type

• Refactor / Cleanup
• DevOps / Deployment / CI
• Testing / QA
• Documentation
• Performance
• Other

---

By submitting this issue, you agree to follow the Apache Code of Conduct.

[Yicong-Huang]

@bobbai00 I still think this may not be manageable. We just handled some version drift two days ago and there are more coming out every day.

Is it good idea to move release level checks (e.g., license binary check) to pre-release branch only? also reduce the frequency (once per week or so). For instance, we only need to start to check this when we start cutting release/v1.2 branch.

[bobbai00]

@bobbai00 I still think this may not be manageable. We just handled some version drift two days ago and there are more coming out every day.

Is it good idea to move release level checks (e.g., license binary check) to pre-release branch only? also reduce the frequency (once per week or so). For instance, we only need to start to check this when we start cutting release/v1.2 branch.

I think the checks should be still on the main branch, otherwise LICENSE-binary can contain many drifts in the main, which is not good.

I agree with you on reducing the frequency to once a week. I can raise a PR for that.