INCATools / INCATools/semantic-sql

[bot] Cut a semsql release including the semanticsql.berkeleybop.io default

Open
#114 2 comments 1 reaction 1 assignee View on GitHub

@caufieldjh is already working on this.

Since Jul 14, 2026.

enhancement
Dominant language
Python
Stars
69
Forks
7
Avg merge
8m
Merged PRs (30d)
1

Description

[bot] Opened by a Claude Code agent on behalf of @kltm.

The `builder.py` download default was repointed to `https://semanticsql.berkeleybop.io` (with a non-`urllib` User-Agent, since the CDN returns 403 to `Python-urllib`) — closing #110 — but that change is on `master` and **not yet released**: PyPI `semsql` latest is still 0.4.0. Until a release is cut, `semsql download` and anything depending on `semsql` still hit the raw S3 bucket.

## Ask

Cut a new `semsql` release to PyPI containing the CDN default so downstream consumers pick it up. This unblocks the migration tracked in #112.

Related: #110, #112, INCATools/ontology-access-kit#880.

_— Posted by Claude Code agent on behalf of @kltm._

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.