Merge remote-tracking branch 'origin/feat-tp' into feat-tp

Author: Andy

.git-blame-ignore-revs

@@ -0,0 +1,21 @@
+# Template taken from https://github.com/v8/v8/blob/master/.git-blame-ignore-revs.
+#
+# This file contains a list of git hashes of revisions to be ignored by git blame. These
+# revisions are considered "unimportant" in that they are unlikely to be what you are
+# interested in when blaming. Most of these will probably be commits related to linting
+# and code formatting.
+#
+# Instructions:
+# - Only large (generally automated) reformatting or renaming CLs should be
+#   added to this list. Do not put things here just because you feel they are
+#   trivial or unimportant. If in doubt, do not put it on this list.
+# - Precede each revision with a comment containing the PR title and number.
+#   For bulk work over many commits, place all commits in a block with a single
+#   comment at the top describing the work done in those commits.
+# - Only put full 40-character hashes on this list (not short hashes or any
+#   other revision reference).
+# - Append to the bottom of the file (revisions should be in chronological order
+#   from oldest to newest).
+# - Because you must use a hash, you need to append to this list in a follow-up
+#   PR to the actual reformatting PR that you are trying to ignore.
+193693836e1ed8cd361e139668323d2e267a9eaa

.github/actions/spelling/allow.txt

@@ -1,12 +1,35 @@
+ACard
+AClient
 AError
 ARequest
+ARun
+AServer
 AStarlette
+EUR
+GBP
+INR
+JPY
+JSONRPCt
+Llm
+aconnect
 adk
+autouse
+cla
+cls
+coc
+codegen
+coro
+datamodel
+dunders
 genai
+gle
 inmemory
 langgraph
 lifecycles
+linting
 oauthoidc
 opensource
 socio
 sse
+tagwords
+vulnz

.github/actions/spelling/excludes.txt

@@ -85,3 +85,5 @@
 ^\Q.github/workflows/linter.yaml\E$
 \.gitignore\E$
 \.vscode/
+noxfile.py
+\.ruff.toml$

.github/conventional-commit-lint.yaml

@@ -0,0 +1,2 @@
+enabled: true
+always_check_pr_title: true

.github/linters/.jscpd.json

@@ -1,5 +1,5 @@
 {
-  "ignore": ["**/.github/**", "**/.git/**", "**/tests/**"],
+  "ignore": ["**/.github/**", "**/.git/**", "**/tests/**", "**/examples/**"],
   "threshold": 3,
   "reporters": ["html", "markdown"]
 }

.github/linters/.markdownlint.json

@@ -0,0 +1,4 @@
+{
+  "MD034": false,
+  "MD013": false
+}

.github/workflows/linter.yaml

@@ -13,9 +13,10 @@ name: Lint Code Base
 #############################
 # Start the job on all push #
 #############################
-on:
-  pull_request:
-    branches: [main]
+# on:
+#   pull_request:
+#     branches: [main]
+on: workflow_dispatch
 
 ###############
 # Set the Job #
@@ -61,3 +62,5 @@ jobs:
           VALIDATE_CHECKOV: false
           VALIDATE_JAVASCRIPT_STANDARD: false
           VALIDATE_TYPESCRIPT_STANDARD: false
+          VALIDATE_GIT_COMMITLINT: false
+          MARKDOWN_CONFIG_FILE: .markdownlint.json

.github/workflows/python-publish.yml

@@ -0,0 +1,54 @@
+name: Publish Python Package
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  contents: read
+
+jobs:
+  release-build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+
+      - name: "Set up Python"
+        uses: actions/setup-python@v5
+        with:
+          python-version-file: "pyproject.toml"
+
+      - name: Build
+        run: uv build
+      
+      - name: Upload distributions
+        uses: actions/upload-artifact@v4
+        with:
+          name: release-dists
+          path: dist/
+
+  pypi-publish:
+    runs-on: ubuntu-latest
+    needs:
+      - release-build
+    permissions:
+      id-token: write
+
+    steps:
+      - name: Retrieve release distributions
+        uses: actions/download-artifact@v4
+        with:
+          name: release-dists
+          path: dist/
+
+      - name: Publish release distributions to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          packages-dir: dist/
+  
+        
+      

.gitignore

@@ -7,4 +7,4 @@ __pycache__
 .ruff_cache
 .venv
 coverage.xml
-spec.json
+.nox

CODE_OF_CONDUCT.md

@@ -3,7 +3,7 @@
 ## Our Pledge
 
 In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
+contributors and maintainers pledge to make participation in our project and
 our community a harassment-free experience for everyone, regardless of age, body
 size, disability, ethnicity, gender identity and expression, level of
 experience, education, socio-economic status, nationality, personal appearance,
@@ -47,7 +47,7 @@ offensive, or harmful.
 
 This Code of Conduct applies both within project spaces and in public spaces
 when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
+representing a project or community include using an official project email
 address, posting via an official social media account, or acting as an appointed
 representative at an online or offline event. Representation of a project may be
 further defined and clarified by project maintainers.
@@ -93,4 +93,4 @@ available at
 https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
 
 Note: A version of this file is also available in the
-[New Project repo](https://github.com/google/new-project/blob/master/docs/code-of-conduct.md).
+[New Project repository](https://github.com/google/new-project/blob/master/docs/code-of-conduct.md).