Update release build workflow

[neuralsorcerer]

Updated the release workflow to build wheels with python -m build instead of deprecated setup.py in both test and deploy jobs.

[Copilot]

Pull request overview

Updates the release GitHub Actions workflow for the balance Python package to use modern PEP 517/518 builds via python -m build, replacing deprecated direct setup.py invocations.

Changes:

• Added an Unreleased (0.17.x) changelog entry noting the workflow packaging update.
• Switched the release workflow’s test and deploy jobs from setup.py wheel builds to python -m build.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
CHANGELOG.md	Adds an Unreleased entry documenting the workflow packaging change and updates release notes formatting.
.github/workflows/release.yml	Replaces setup.py build commands with python -m build in both test and deploy jobs.

[meta-codesync]

@talgalili has imported this pull request. If you are a Meta employee, you can view this in D92711564.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

[neuralsorcerer]

@talgalili sorry my bad. The current commit in the main branch is correct. We need to update here

[neuralsorcerer]

We can close this PR.

[talgalili]

@neuralsorcerer the current main branch solution is not working.
https://github.com/facebookresearch/balance/blob/0.16.0/.github/workflows/release.yml

I'm landing the current PR (the one you just closed - it's about to be landed).
Should I cancel the land?

[neuralsorcerer]

Please cancel this land.

[neuralsorcerer]

Created new PR #332

[talgalili]

@neuralsorcerer I stopped the land.
Could you please fix this so it would work - in the current PR?

[neuralsorcerer]

@talgalili We need to push the changes in main branch to 0.16 tagged version

[talgalili]

@neuralsorcerer I removed the 0.16 tag.
You tell me when I can land this - once I do - I'll re-release 0.16

[talgalili]

@neuralsorcerer so to clarify, it's fine that I'll land:
#329
And then create a 0.16 tag?

[neuralsorcerer]

@talgalili the current commit in the main branch is good. No need to land this PR. Previously, the release was created before the fix to main branch, that's why the deploy was failing.