Skip to content

ci: fixed prepare client dir stage - #6

Merged
susek555 merged 1 commit into
mainfrom
3-improve-ci
Dec 19, 2025
Merged

ci: fixed prepare client dir stage#6
susek555 merged 1 commit into
mainfrom
3-improve-ci

Conversation

@susek555

Copy link
Copy Markdown
Contributor

No description provided.

@susek555 susek555 self-assigned this Dec 19, 2025
@susek555
susek555 requested a review from Copilot December 19, 2025 15:36
@susek555
susek555 merged commit 7f980ee into main Dec 19, 2025
11 checks passed

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

This PR fixes the "Prepare Client Directory" stage in the CI workflow by adding necessary files to the Python release directory and cleaning up build artifacts.

Key changes:

  • Adds workflow file (publish.yml) and optional LICENSE file to the release directory
  • Removes uv.lock from the release to exclude build-specific dependencies
  • Removes a debug grep command that was checking the version string

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

rm -rf python_release/tests
find python_release -type d -name "__pycache__" -exec rm -rf {} +
rm -rf python_release/.venv
rm -rf python_release/uv.lock

Copilot AI Dec 19, 2025

Copy link

Choose a reason for hiding this comment

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

Removing uv.lock may cause issues with the publish.yml workflow which references "uv.lock" in the cache-dependency-glob configuration. While the publish workflow should still work, the absence of uv.lock will prevent proper cache invalidation based on dependency changes and may lead to using stale cached dependencies. Consider whether uv.lock should be included in the release or if the publish.yml cache configuration should be updated.

Suggested change
rm -rf python_release/uv.lock

Copilot uses AI. Check for mistakes.
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