release: prepare SDK v1.7.0 for Workflow Evals

[joaomarcoscrs]

Description

Prepare SDK 1.7.0 to ship Workflow Evals support from #540. That PR is merged into main but is not included in the published v1.6.1 tag. The complete unreleased range contains only #540.

Bump the shared package version and add the changelog entry for the SDK client, CLI commands, and workspace access/API-key scope requirements. Both roboflow and roboflow-slim read this version. Use a minor release for the new SDK and CLI functionality.

Type of change

• Maintenance (release preparation)

How has this change been tested, please provide a testcase or example of how you tested the change?

• Python 3.12: python -m unittest passes 1,163 tests with one expected skip; make style and make check_code_quality pass Ruff and mypy.
• Built sdists and wheels for both distributions; twine check passes all four artifacts. Wheel metadata reads 1.7.0 and both archive types include the Workflow Evals SDK, transport, and CLI modules.
• Installed each wheel into its own clean environment. Verified installed metadata/imported version, SDK helper availability, CLI version, and Workflow Evals discovery/import/run help without credentials or platform writes.

Will the change affect Universe? If so was this change tested in universe?

No.

Any specific deployment considerations

• After this PR is approved, CI is green, and it is merged, create a GitHub release tagged v1.7.0 at the merge commit that contains this version bump. Generate notes since v1.6.1, including the Workflow Evals entry from CHANGELOG.md.
• Publishing the GitHub release triggers .github/workflows/publish.yml: build publishes roboflow, build-slim then publishes roboflow-slim, and deploy-docs publishes the SDK documentation. No manual PyPI token or local upload is needed.
• Confirm both PyPI projects show 1.7.0 and the installed CLI exposes roboflow workflow-eval after publication. Workflow Evals still requires workspace access and the appropriate scopes.
• This PR prepares the release; it does not publish it.

Infrastructure impact

• This change affects infrastructure needs (GPUs, Cloud Function sizing, storage etc.)

[joaomarcoscrs]

[Jarbas Local João] — APPROVED at cfc690414734

Gist: https://gist.github.com/joaomarcoscrs/8dd7bbe44c6a96f92502b9560396af32