LLMstudio Core Version 1.1.0 - Agents Wrapper

.github/workflows/tests.yml

@@ -0,0 +1,41 @@
+name: Tests
+
+on:
+  pull_request:
+    branches:
+      - main
+    types:
+      - opened
+      - synchronize
+      - reopened
+
+jobs:
+  tests:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+
+      # Set up Python environment
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: "3.x"
+
+      # Install Poetry
+      - name: Install Poetry
+        run: |
+          curl -sSL https://install.python-poetry.org | python3 -
+      # Install lib and dev dependencies
+      - name: Install llmstudio-core
+        working-directory: ./libs/core
+        run: |
+          poetry install
+          POETRY_ENV=$(poetry env info --path)
+          echo $POETRY_ENV
+          echo "POETRY_ENV=$POETRY_ENV" >> $GITHUB_ENV
+
+      - name: Run unit tests
+        run: |
+          echo ${{ env.POETRY_ENV }}
+          source ${{ env.POETRY_ENV }}/bin/activate
+          poetry run pytest libs/core

.github/workflows/upload-pypi-dev.yml

@@ -1,4 +1,4 @@
-name: PyPI prerelease and build/push Docker image.
+name: PyPI prerelease any module.
 
 on:
   workflow_dispatch:

.gitignore

@@ -56,6 +56,7 @@ env3
 .env*
 .env*.local
 .venv*
+*venv*
 env*/
 venv*/
 ENV/
@@ -66,6 +67,7 @@ venv.bak/
 config.yaml
 bun.lockb
 
+
 # Jupyter Notebook
 .ipynb_checkpoints
 
@@ -76,4 +78,4 @@ bun.lockb
 llmstudio/llm_engine/logs/execution_logs.jsonl
 *.db
 .prettierignore
-db
+db

CONTRIBUTING.md

@@ -9,9 +9,30 @@ Thank you for expressing your interest in contributing to LLMstudio. To ensure t
 3. Follow our repo guidelines
    - Ensure that you update any relevant docstrings and comments within your code
    - Run `pre-commit run --all-files` to lint your code
+4. Sign your commits. Without signed commits, your changes will not be accepted for main.
 
 ## Branches
 
 - All development happens in per-feature branches prefixed by contributor's
   initials. For example `feat/feature_name`.
 - Approved PRs are merged to the `main` branch.
+
+## Alpha releases:
+You need to have your changes in the `develop` branch in order to push a new alpha version of any library `(llmstudio, llmstudio-proxy, llmstudio-tracker)`. Therefore, first guarantee that you feature branch is reviewed and working before merging to develop.
+
+Process:
+- Ensure the `feature/**` you worked is passing the tests and has the approvals necessary.
+- Merge to `develop`
+- Ensure the changes are in the develop branch
+- Use GitHub Actions to initiate the pre-release process: [PyPI pre-release any module](https://github.com/TensorOpsAI/LLMstudio/actions/workflows/upload-pypi-dev.yml)
+- Select the target library `(llmstudio, llmstudio-proxy, llmstudio-tracker)` and the target version for the final release (e.g., 1.1.0). Consult main branch and PyPI for current versions.
+- Run the workflow.
+- The workflow will automatically bump the version and create an alpha release of the library/module specified
+- The workflow will automatically push changes back (bump version) to the develop branch
+
+Repeat the process in case your `development` branch contains changes in multiple libraries.
+
+## Final releases:
+Once you're happy with the versions, create the Release notes on the PR between `develop` and `main` and merge to main branch when ready for full release. The workflow will automatically remove any `alpha` tag in your libraries and push the versions for every library/module that suffered changes.
+
+

Makefile

@@ -1,2 +1,5 @@
 format:
 	pre-commit run --all-files
+
+unit-tests:
+	pytest libs/core/tests/unit_tests