galileo-core (in Orbit)

Shared schemas and configuration for Galileo's Python packages.

This package is now maintained inside the Orbit monorepo at libs/python/core/.

Package Layout

libs/python/core/
├── BUILD.bazel
├── README.md
├── galileo_core/
│   ├── __init__.py
│   ├── schemas/
│   ├── helpers/
│   ├── constants/
│   ├── exceptions/
│   ├── utils/
│   └── testing/
└── tests/

Running Tests

Orbit is Bazel-first. Run tests with Bazel:

# Run core package tests
bazel test //libs/python/core:core_test

# Or run all tests in orbit
bazel test //...

Building Distribution Artifacts

Build the wheel target with Bazel:

bazel build //libs/python/core:galileo_core_wheel

Custom HTTP Headers (API gateways / IBM APIC)

When the Galileo API is fronted by a gateway (e.g. IBM APIC) that requires extra routing or auth headers, set GALILEO_EXTRA_HEADERS to a JSON object mapping header names to values. These headers are sent on every request that goes through galileo_core's ApiClient — that is, all core-backed flows: login, the pre-auth healthcheck, token refresh, resource calls, and batch ingestion:

export GALILEO_EXTRA_HEADERS='{"ibm_client_id": "my_client_id", "ibm_client_secret": "my_client_secret"}'

Or pass them programmatically via the extra_headers config argument. Galileo's own auth/content headers always take precedence on key collisions and cannot be overridden.

Scope: this applies to requests issued through galileo_core.helpers.api_client.ApiClient. Legacy egress paths that build their own HTTP client (e.g. setgalileo's assistant-tool requests) do not read GalileoConfig.extra_headers and are not covered here.

Import Path

The import path remains:

import galileo_core

This stays the same for both internal Orbit usage and external PyPI consumers.

Publishing

galileo-core is published to public PyPI from Orbit workflows.

Use the Orbit PyPI Release workflow (.github/workflows/orbit-pypi-release.yaml):

Trigger manually from main only.
Set package=core.
Leave bump empty to auto-infer semver from commits, or set major|minor|patch to override.

The workflow updates libs/python/core/version.bzl, creates a vX.Y.Z tag, builds //libs/python/core:galileo_core_wheel, and publishes to PyPI.

Metadata

Release files for galileo-core 4.5.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for galileo-core 4.5.0
File	Interpreter	ABI	Platform	Reset
galileo_core-4.5.0-py3-none-any.whl 116.0 kB Jul 30, 2026	Python 3	none	any	Details

Release files / galileo_core-4.5.0-py3-none-any.whl

Download URL	galileo_core-4.5.0-py3-none-any.whl
Size	116.0 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`226d45cc328d661ff3c81dbd517ded8707a8dbd5f33f477b11c646e3ee190a9d`
BLAKE2b-256 checksum How to use checksums	`150ef7f73b9e15676a7905239f3c54eb4b920c2e94a73f4df2bc630722550761`
Upload date	Jul 30, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/rungalileo/orbit
Publishing commit: github.com/rungalileo/orbit/tree/34fee0a2989a2f696f9104abf8eae0e516a840b4

Workflow

Publishing configuration: github.com/rungalileo/orbit/blob/34fee0a2989a2f696f9104abf8eae0e516a840b4/.github/workflows/orbit-pypi-release.yaml
Publishing logs: github.com/rungalileo/orbit/actions/runs/30568018654/attempts/1

Artifact

Subject: galileo_core-4.5.0-py3-none-any.whl
SHA-256 checksum: 226d45cc328d661ff3c81dbd517ded8707a8dbd5f33f477b11c646e3ee190a9d Verifying attestations