graphora 0.0.0__tar.gz

graphora-0.0.0/.github/workflows/publish.yml

@@ -0,0 +1,96 @@
+name: Publish to PyPI
+
+on:
+  workflow_dispatch:
+    inputs:
+      bump:
+        description: "Version bump type"
+        required: true
+        type: choice
+        options:
+          - patch
+          - minor
+          - major
+      dry_run:
+        description: "Dry run (build only, don't upload)"
+        required: false
+        type: boolean
+        default: false
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      id-token: write
+
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          fetch-tags: true
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Install build tools
+        run: pip install build twine setuptools-scm
+
+      - name: Compute next version
+        id: version
+        run: |
+          # Get latest version tag (fallback to 0.0.0 if none)
+          LATEST=$(git tag -l 'v*' --sort=-v:refname | head -1 | sed 's/^v//')
+          if [ -z "$LATEST" ]; then
+            LATEST="0.0.0"
+          fi
+
+          IFS='.' read -r MAJOR MINOR PATCH <<< "$LATEST"
+
+          case "${{ inputs.bump }}" in
+            major) MAJOR=$((MAJOR + 1)); MINOR=0; PATCH=0 ;;
+            minor) MINOR=$((MINOR + 1)); PATCH=0 ;;
+            patch) PATCH=$((PATCH + 1)) ;;
+          esac
+
+          NEXT="${MAJOR}.${MINOR}.${PATCH}"
+          echo "version=$NEXT" >> "$GITHUB_OUTPUT"
+          echo "tag=v$NEXT" >> "$GITHUB_OUTPUT"
+          echo "Bumping $LATEST → $NEXT (${{ inputs.bump }})"
+
+      - name: Create version tag
+        run: |
+          git config user.name "github-actions"
+          git config user.email "github-actions@github.com"
+          git tag -a "${{ steps.version.outputs.tag }}" -m "Release ${{ steps.version.outputs.tag }}"
+
+      - name: Build package
+        run: python -m build
+
+      - name: Verify version
+        run: |
+          BUILT=$(python -c "from setuptools_scm import get_version; print(get_version())")
+          echo "Built version: $BUILT"
+          EXPECTED="${{ steps.version.outputs.version }}"
+          if [ "$BUILT" != "$EXPECTED" ]; then
+            echo "::error::Version mismatch: built=$BUILT expected=$EXPECTED"
+            exit 1
+          fi
+
+      - name: Check package
+        run: twine check dist/*
+
+      - name: Publish to PyPI
+        if: ${{ !inputs.dry_run }}
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          password: ${{ secrets.PYPI_API_TOKEN }}
+
+      - name: Push version tag
+        if: ${{ !inputs.dry_run }}
+        run: git push origin "${{ steps.version.outputs.tag }}"
+
+      - name: Clean up tag on dry run
+        if: ${{ inputs.dry_run }}
+        run: git tag -d "${{ steps.version.outputs.tag }}"

graphora-0.0.0/.gitignore

@@ -0,0 +1,174 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/latest/usage/project/#working-with-version-control
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc

graphora-0.0.0/CLA.md

@@ -0,0 +1,97 @@
+# Contributor License Agreement (CLA)
+
+Thank you for your interest in contributing to Graphora (the "Project"). This Contributor License Agreement ("Agreement") documents the rights granted by contributors to Arivan Labs.
+
+## Why Do We Need a CLA?
+
+This CLA allows us to:
+- Offer Graphora under both open source (AGPL v3) and commercial licenses
+- Protect the project and all its users from legal issues
+- Ensure we have the rights to distribute your contributions
+- Maintain the ability to change the license if necessary for the project's health
+
+## Agreement
+
+By submitting a contribution to this project, you agree to the following terms and conditions for your present and future contributions:
+
+### 1. Definitions
+
+**"You"** (or **"Your"**) means the copyright owner or legal entity authorized by the copyright owner that is making this Agreement.
+
+**"Contribution"** means any original work of authorship, including any modifications or additions to an existing work, that is intentionally submitted by You to the Project for inclusion in, or documentation of, the Project.
+
+**"Submit"** means any form of electronic, verbal, or written communication sent to the Project, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems.
+
+### 2. Grant of Copyright License
+
+You hereby grant to Arivan Labs and to recipients of software distributed by Arivan Labs a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Your Contributions and such derivative works under any license, including without limitation:
+- The GNU Affero General Public License v3 (AGPL v3)
+- Any future version of the AGPL
+- A proprietary commercial license
+
+### 3. Grant of Patent License
+
+You hereby grant to Arivan Labs and to recipients of software distributed by Arivan Labs a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by You that are necessarily infringed by Your Contribution(s) alone or by combination of Your Contribution(s) with the Work to which such Contribution(s) was submitted.
+
+### 4. Representations
+
+You represent that:
+
+a) You are legally entitled to grant the above licenses.
+
+b) Each of Your Contributions is Your original creation (see section 6 for submissions on behalf of others).
+
+c) Your Contribution submissions include complete details of any third-party license or other restriction (including, but not limited to, related patents and trademarks) of which you are personally aware and which are associated with any part of Your Contributions.
+
+d) If Your employer(s) has rights to intellectual property that you create that includes your Contributions, you represent that you have received permission to make Contributions on behalf of that employer, or that your employer has waived such rights for your Contributions to the Project.
+
+### 5. Support
+
+You are not expected to provide support for Your Contributions, except to the extent You desire to provide support. You may provide support for free, for a fee, or not at all. Unless required by applicable law or agreed to in writing, You provide Your Contributions on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE.
+
+### 6. Third-Party Works
+
+Should You wish to submit work that is not Your original creation, You may submit it to the Project separately from any Contribution, identifying the complete details of its source and of any license or other restriction (including, but not limited to, related patents, trademarks, and license agreements) of which you are personally aware, and conspicuously marking the work as "Submitted on behalf of a third-party: [named here]".
+
+### 7. Notification
+
+You agree to notify Arivan Labs of any facts or circumstances of which you become aware that would make these representations inaccurate in any respect.
+
+---
+
+## How to Sign
+
+### For Individual Contributors
+
+By adding the following line to your pull request description, you acknowledge that you have read and agree to this CLA:
+
+```
+I have read and agree to the Contributor License Agreement.
+```
+
+Alternatively, you may send an email to `support@graphora.io` with the following information:
+- Your full name
+- Your email address
+- GitHub username
+- The statement: "I have read and agree to the Contributor License Agreement"
+
+### For Corporate Contributors
+
+If you are contributing on behalf of a corporation, your authorized representative must send an email to `support@graphora.io` with:
+- Corporation name
+- Authorized signatory name and title
+- List of employees authorized to contribute (or "*" for all employees)
+- Corporate email domain
+- The statement: "On behalf of [Corporation Name], I have read and agree to the Corporate Contributor License Agreement"
+
+We will maintain a public record of CLA signatories (individual names and corporate entities only, not email addresses).
+
+---
+
+## Corporate Contributor License Agreement
+
+For corporations wishing to contribute, please download and sign the [Corporate CLA](CLA-CORPORATE.md) and send it to `support@graphora.io`.
+
+---
+
+**Questions?** Contact us at `support@graphora.io` or open an issue in the repository.