Skip to content

Conversation

@davahiatak1
Copy link

No description provided.

aksg87 and others added 28 commits July 22, 2025 01:39
- Switch from badge.fury.io to shields.io for working PyPI badge
- Convert relative paths to absolute GitHub URLs for PyPI compatibility
- Bump version to 0.1.3
- Add GitHub Actions workflow for automated PyPI publishing via OIDC
- Configure trusted publishing environment for verified releases
- Update project metadata with proper URLs and license format
- Prepare for v1.0.0 stable release with production-ready automation
- Add pylibmagic>=0.5.0 dependency for bundled libraries
- Add [full] install option and pre-import handling
- Update README with troubleshooting and Docker sections
- Bump version to 1.0.1

Fixes google#6
Deleted an inline comment referencing the  output directory in the save_annotated_documents.
…ples.md

docs: clarify output_dir behavior in medication_examples.md
Prevents confusion from default `test_output/...` by explicitly saving to current directory.
docs: add output_dir="." to all save_annotated_documents examples
feat: add code formatting and linting pipeline
Introduces a common base exception class that all library-specific exceptions inherit from, enabling users to catch all LangExtract errors with a single except clause.
Add LangExtractError base exception for centralized error handling
Fixes google#25 - Windows installation failure due to pylibmagic build requirements

Breaking change: LangFunLanguageModel removed. Use GeminiLanguageModel or OllamaLanguageModel instead.
fix: Remove LangFun and pylibmagic dependencies to fix Windows installation and OpenAI SDK v1.x compatibility
- Modified save_annotated_documents to accept both pathlib.Path and string paths
- Convert string paths to Path objects before calling mkdir()
- This fixes the error when using output_dir='.' as shown in the README example
…-mkdir

Fix save_annotated_documents to handle string paths
feat: Add OpenAI language model support
…s: (google#10)

* docs: clarify output_dir behavior in medication_examples.md

* Removed inline comment in medication example

Deleted an inline comment referencing the  output directory in the save_annotated_documents.

* docs: add output_dir="." to all save_annotated_documents examples

Prevents confusion from default `test_output/...` by explicitly saving to current directory.

* build: add formatting & linting pipeline with pre-commit integration

* style: apply pyink, isort, and pre-commit formatting

* ci: enable format and lint checks in tox

* Add LangExtractError base exception for centralized error handling

Introduces a common base exception class that all library-specific exceptions inherit from, enabling users to catch all LangExtract errors with a single except clause.

* fix(ui): prevent current highlight border from being obscured

---------

Co-authored-by: Leena Kamran <[email protected]>
Co-authored-by: Akshay Goel <[email protected]>
- Gemini & OpenAI test suites with retry on transient errors
- CI: Separate job, Python 3.11 only, skips for forks
- Validates char_interval for all extractions
- Multilingual test xfail (issue google#13)

TODO: Remove xfail from multilingual test after tokenizer fix
…e#62)

- Add quickstart example and documentation for local LLM usage
- Include Docker setup with health checks and docker-compose
- Add integration tests and update CI pipeline
- Secure setup: localhost-only binding, containerized deployment

Signed-off-by: Akshay Goel <[email protected]>
- Ollama integration with Docker examples
- Fixed OllamaLanguageModel parameter name (model -> model_id)
- Added CI/CD tests for Ollama
- Updated documentation with consistent API examples
@google-cla
Copy link

google-cla bot commented Oct 28, 2025

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@github-actions
Copy link

No linked issues found. Please link an issue in your pull request description or title.

Per our Contributing Guidelines, all PRs must:

  • Reference an issue with one of:
    • Closing keywords: Fixes #123, Closes #123, Resolves #123 (auto-closes on merge in the same repository)
    • Reference keywords: Related to #123, Refs #123, Part of #123, See #123 (links without closing)
  • The linked issue should have 5+ 👍 reactions from unique users (excluding bots and the PR author)
  • Include discussion demonstrating the importance of the change

You can also use cross-repo references like owner/repo#123 or full URLs.

@github-actions github-actions bot added the size/XL Pull request with over 1000 lines changed - too large label Oct 28, 2025
@github-actions
Copy link

Infrastructure File Protection

This PR modifies protected infrastructure files:

  • .github/ISSUE_TEMPLATE/config.yml (2 changes)
  • .github/workflows/ci.yaml (91 changes)
  • .github/workflows/publish.yml (55 changes)
  • .github/workflows/validate_pr_template.yaml (41 changes)
  • .gitignore (2 changes)
  • .pre-commit-config.yaml (46 changes)
  • .pylintrc (414 changes)
  • CITATION.cff (28 changes)
  • CONTRIBUTING.md (102 changes)
  • Dockerfile (11 changes)
  • autoformat.sh (125 changes)

Only repository maintainers are allowed to modify infrastructure files (including .github/, build configuration, and repository documentation).

Note: If these are only formatting changes, please:

  1. Revert changes to .github/ files
  2. Use ./autoformat.sh to format only source code directories
  3. Avoid running formatters on infrastructure files

If structural changes are necessary:

  1. Open an issue describing the needed infrastructure changes
  2. A maintainer will review and implement the changes if approved

For more information, see our Contributing Guidelines.

@github-actions
Copy link

⚠️ Branch Update Required

Your branch is 111 commits behind main. Please update your branch to ensure CI checks run with the latest code:

git fetch origin main
git merge origin/main
git push

Note: Enable "Allow edits by maintainers" to allow automatic updates.

@github-actions
Copy link

github-actions bot commented Nov 6, 2025

⚠️ Branch Update Required

Your branch is 114 commits behind main. Please update your branch to ensure CI checks run with the latest code:

git fetch origin main
git merge origin/main
git push

Note: Enable "Allow edits by maintainers" to allow automatic updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/XL Pull request with over 1000 lines changed - too large

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants