Skip to content

stop hardcoding versions #2 - #75

Merged
maxlastglance merged 45 commits into
release-1.14from
main
Jul 24, 2026
Merged

stop hardcoding versions #2#75
maxlastglance merged 45 commits into
release-1.14from
main

Conversation

@s-tittel

@s-tittel s-tittel commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Description

Please provide a brief description of the changes in this pull request.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Refactoring (no functional changes, no API changes)
  • Dependency update

Related Issue

Closes # (issue number)

Checklist

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Additional Notes

Add any additional notes or context here.

maxlastglance and others added 23 commits June 9, 2026 13:33
- Dashboard service
- Search service
- Python library
- Dashboard service Dockerfile and init Dockerfile
- Search service Dockerfile and init Dockerfile
- Storage service init Dockerfile
The image does not exist on docker.io anymore.
To reenable: restore open-pull-requests-limit to 10 in
.github/dependabot.yml
- remove code coverage as this is currently non-functional
- add badge for release workflow
- update license badge
`make build-images` needs to be run, otherwise DuckDB extensions are not
copied and `docker compose build` fails.
bun.lockdb created with current bun 1.3 branch shipped with recent OS
versions is incompatible with 1.2 and vice-versa. Regenerating lockdb
hence breaks `docker compose build`.
The production schema bootstrap omitted CREATE TABLE for mdb_concepts,
mdb_units, mdb_columns_concepts, and mdb_columns_units. The delete-table
cascade issues native DELETEs against mdb_columns_concepts and
mdb_columns_units, which caused MariaDB error 1146 (table doesn't exist)
on every table delete, aborting the transaction and returning HTTP 500.

Added CREATE TABLE IF NOT EXISTS for all four tables in dependency order,
mirroring the live-image bootstrap definitions.
…db schema

Helm chart maintains a separate copy of the metadata-db schema at
helm/dbrepo/files/01-setup-schema.sql, loaded via the metadata-db-config
ConfigMap (templates/metadata-db-configmap.yaml). This copy was missing
the same four tables (mdb_concepts, mdb_units, mdb_columns_concepts,
mdb_columns_units) as the docker-compose bootstrap, so Kubernetes
deployments hit the same MariaDB 1146 error on table delete.

Applied the same fix as the docker-compose schema: added CREATE TABLE
IF NOT EXISTS for all four tables in dependency order, mirroring the
live-image bootstrap definitions.
…ipt-url-in-readmemd

Update README.md for GitHub migration changes
Add GitHub workflow to publish Python client to PyPI
Athemis and others added 18 commits July 12, 2026 23:22
…drops-ownership-and-fails-search-indexing

fix(metadata): preserve table ownership during refresh
…s-invalid-databasebrief-with-null-contact

fix(metadata): preserve contact in refresh response
…-refresh-fails

fix(data): handle null tables during exploration
…ails

fix(install): fix download location in install script
fix(helm): configure data service cache port
@maxlastglance
maxlastglance merged commit 9c8499e into release-1.14 Jul 24, 2026
34 checks passed
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.

3 participants