Skip to content

chore(release): release main#497

Merged
Hoeze merged 1 commit into
mainfrom
release-please--branches--main
May 12, 2026
Merged

chore(release): release main#497
Hoeze merged 1 commit into
mainfrom
release-please--branches--main

Conversation

@MVHBot

@MVHBot MVHBot commented Jan 30, 2026

Copy link
Copy Markdown
Contributor

grz-tools release (2026-05-11)

This release updates multiple packages in the grz-tools monorepo. See the full changelog and per-package details linked below.

Versions

  • grzctl 2.0.0 (from 1.4.0)
  • grz-db 2.0.0 (from 1.2.0)
  • grz-common 2.0.0 (from 1.6.1)
  • grz-cli 1.6.0 (from 1.5.1)
  • grz-pydantic-models 2.6.0 (from 2.5.0)
  • grz-check 0.3.0 (from 0.2.1)

⚠️ Breaking / behavior changes


Highlights

grz-cli (1.6.0)

grzctl (2.0.0)

grz-pydantic-models (2.6.0)

grz-check (0.3.0)

Maintenance


Rollout notes (ops)

  • Apply the submission DB migrations before using this release. The schema changes include selected_for_qc, QC workflow version logging, grzctl runtime version logging, and the new REPORTING state.
  • Submission DB migrations in this release also include the qc_queue table and additional submissions fields (submission_size, submission_metadata)—make sure your DB is migrated to head before running the updated tools.
  • Update any automation that calls grzctl pruefbericht submit to pass --submission-id.
  • If you enforce LE uploads via S3, deploy the version.json policy for grz-cli.
  • Deploy the matching grz-check Python bindings where Python-based checksum validation is used.

Full details

@MVHBot MVHBot force-pushed the release-please--branches--main branch 7 times, most recently from 32c9472 to 2ad8d0a Compare February 5, 2026 16:24
@MVHBot MVHBot force-pushed the release-please--branches--main branch from 2ad8d0a to 7804ae1 Compare February 12, 2026 16:40
@MVHBot MVHBot force-pushed the release-please--branches--main branch 3 times, most recently from e0763bc to 4e4ccde Compare February 26, 2026 10:24
@MVHBot MVHBot force-pushed the release-please--branches--main branch 2 times, most recently from 67159d6 to ee9858f Compare March 3, 2026 15:57
@MVHBot MVHBot force-pushed the release-please--branches--main branch 3 times, most recently from 49260c5 to 9a39afe Compare March 25, 2026 09:48
@MVHBot MVHBot force-pushed the release-please--branches--main branch 2 times, most recently from 2582fad to f7af733 Compare April 15, 2026 08:52
@MVHBot MVHBot force-pushed the release-please--branches--main branch 6 times, most recently from e53135f to c84da35 Compare April 29, 2026 09:56
@MVHBot MVHBot force-pushed the release-please--branches--main branch 5 times, most recently from 9c434cc to da2b4e4 Compare May 8, 2026 10:40
@MVHBot MVHBot force-pushed the release-please--branches--main branch from 653d70d to acd5f94 Compare May 11, 2026 15:08
@Hoeze Hoeze enabled auto-merge May 12, 2026 11:01
@Hoeze Hoeze added this pull request to the merge queue May 12, 2026
Merged via the queue into main with commit 6b8f89c May 12, 2026
19 checks passed
@Hoeze Hoeze deleted the release-please--branches--main branch May 12, 2026 11:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants