Skip to content

feat: Add --clean flag for node directory cleanup and dynamic folder name from version#622

Merged
sazid merged 4 commits intodevfrom
zeuz-node-versioning
Dec 2, 2025
Merged

feat: Add --clean flag for node directory cleanup and dynamic folder name from version#622
sazid merged 4 commits intodevfrom
zeuz-node-versioning

Conversation

@mahbd
Copy link
Copy Markdown
Collaborator

@mahbd mahbd commented Nov 23, 2025

PR Type

Feature

PR Checklist

  • Tests for the changes have been added / updated.
  • Documentation comments have been added / updated.
  • A changelog entry has been made.
  • Version number has been updated.
  • Required modules have been added to respective "requirements*.txt" files.
  • Relevant Test Cases added to this description (below).
  • (Team) Label with affected action categories and semver status.

Overview

Previously when running ZeuzNode it used to create a directory name ZeuZ_Python_Node. The directory was same regardless of directory. The problem was if we want to upgrade to new version we need to delete the existing version. This is little bit inconvenience. Also deleting the old directory will erase the history. So we introduced versioning.

Also we introduced new flag named -clean. If we pass this tag when running the binary, it will clean the .zeuz and ZeuZ_Python_Node-v$(version).

Now by default when building if nothing is passed then version will be taken from Version.txt file in the Makefile.

…-based directory naming with Makefile version sourcing.
@mahbd mahbd changed the title feat: Add --clean flag for node directory cleanup and dynamic versioning feat: Add --clean flag for node directory cleanup and dynamic folder name from version Nov 23, 2025
@sazid sazid merged commit c01d87d into dev Dec 2, 2025
7 checks passed
@sazid sazid deleted the zeuz-node-versioning branch December 2, 2025 11:22
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