Skip to content

add frontend for search#3

Draft
isaacbmiller wants to merge 1 commit into12-04-demo_f9585677_add_server_apifrom
12-04-demo_549e89f3_add_frontend_for_search
Draft

add frontend for search#3
isaacbmiller wants to merge 1 commit into12-04-demo_f9585677_add_server_apifrom
12-04-demo_549e89f3_add_frontend_for_search

Conversation

@isaacbmiller
Copy link
Copy Markdown

📝 Changes Description

This MR/PR contains the following changes:
...

✅ Contributor Checklist

  • [] Pre-Commit checks are passing (locally and remotely)
  • [] Title of your PR / MR corresponds to the required format
  • [] Commit message follows required format {label}(dspy): {message}

⚠️ Warnings

Anything we should be aware of ?

@isaacbmiller isaacbmiller mentioned this pull request Dec 4, 2025
Copy link
Copy Markdown
Author

isaacbmiller commented Dec 4, 2025

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

This stack of pull requests is managed by Graphite. Learn more about stacking.

@isaacbmiller isaacbmiller force-pushed the 12-04-demo_f9585677_add_server_api branch from c644a91 to dea6cec Compare December 4, 2025 17:12
@isaacbmiller isaacbmiller force-pushed the 12-04-demo_549e89f3_add_frontend_for_search branch from 2d45cc8 to 7afd68a Compare December 4, 2025 17:12
@isaacbmiller isaacbmiller mentioned this pull request Dec 4, 2025
isaacbmiller added a commit that referenced this pull request Apr 22, 2026
Refactors the release workflow so the jobs that hold id-token: write for
PyPI Trusted Publishing have only two steps: download the pre-built
distribution artifacts and invoke pypa/gh-action-pypi-publish. This
matches PyPA and PyPI security-model guidance to minimize the privileged
blast radius.

Job graph:

  extract-tag -> build -> test-wheel -> publish-testpypi -> publish-pypi -> sync-version-to-main

- build (no id-token, no contents:write): performs the sed-based
  version/name patching, builds and validates three dist sets
  (dspy-ai-test-isaac for TestPyPI; dspy and dspy-ai for PyPI), and
  uploads each as a named artifact.
- test-wheel (no privileged permissions): downloads the real dspy wheel
  and runs the existing pytest subset against it.
- publish-testpypi (id-token: write only, environment testpypi): 2 steps
  - download + upload to TestPyPI.
- publish-pypi (id-token: write only, environment pypi): 4 steps -
  download dspy artifacts + publish, download dspy-ai artifacts + publish.
- sync-version-to-main (contents: write only): unchanged from PR #3.

Refs PyPI security-model guidance: https://docs.pypi.org/trusted-publishers/security-model/
('Limit the scope of your publishing job').
Refs PyPA publishing guide: https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
isaacbmiller added a commit that referenced this pull request Apr 22, 2026
Refactors the release workflow so the jobs that hold id-token: write for
PyPI Trusted Publishing have only two steps: download the pre-built
distribution artifacts and invoke pypa/gh-action-pypi-publish. This
matches PyPA and PyPI security-model guidance to minimize the privileged
blast radius.

Job graph:

  extract-tag -> build -> test-wheel -> publish-testpypi -> publish-pypi -> sync-version-to-main

- build (no id-token, no contents:write): performs the sed-based
  version/name patching, builds and validates three dist sets
  (dspy-ai-test-isaac for TestPyPI; dspy and dspy-ai for PyPI), and
  uploads each as a named artifact.
- test-wheel (no privileged permissions): downloads the real dspy wheel
  and runs the existing pytest subset against it.
- publish-testpypi (id-token: write only, environment testpypi): 2 steps
  - download + upload to TestPyPI.
- publish-pypi (id-token: write only, environment pypi): 4 steps -
  download dspy artifacts + publish, download dspy-ai artifacts + publish.
- sync-version-to-main (contents: write only): unchanged from PR #3.

Refs PyPI security-model guidance: https://docs.pypi.org/trusted-publishers/security-model/
('Limit the scope of your publishing job').
Refs PyPA publishing guide: https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
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.

1 participant