chore(deps)(deps): Bump org.xerial:sqlite-jdbc from 3.49.1.0 to 3.53.0.0 in /core - #3
Merged
gkrost merged 1 commit intoMay 1, 2026
Conversation
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
dependabot
Bot
force-pushed
the
dependabot/gradle/core/org.xerial-sqlite-jdbc-3.53.0.0
branch
from
May 1, 2026 08:31
85b7aea to
230940a
Compare
Bumps [org.xerial:sqlite-jdbc](https://github.com/xerial/sqlite-jdbc) from 3.49.1.0 to 3.53.0.0. - [Release notes](https://github.com/xerial/sqlite-jdbc/releases) - [Changelog](https://github.com/xerial/sqlite-jdbc/blob/master/CHANGELOG) - [Commits](xerial/sqlite-jdbc@3.49.1.0...3.53.0.0) --- updated-dependencies: - dependency-name: org.xerial:sqlite-jdbc dependency-version: 3.53.0.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/gradle/core/org.xerial-sqlite-jdbc-3.53.0.0
branch
from
May 1, 2026 09:16
230940a to
3819f62
Compare
dependabot
Bot
deleted the
dependabot/gradle/core/org.xerial-sqlite-jdbc-3.53.0.0
branch
May 1, 2026 18:30
gkrost
added a commit
that referenced
this pull request
May 2, 2026
Merge of main brought kotlin 2.3.20→2.3.21 (#2), ktor 3.4.2→3.4.3 (#1) and sqlite-jdbc 3.49.1.0→3.53.0.0 (#3) into libs.versions.toml. The 12 per-module gradle.lockfile files still pinned the old versions, which made CI's PR-merge preview fail with: Could not resolve org.jetbrains.kotlin:kotlin-stdlib:2.3.21. Constraint path: ... 'org.jetbrains.kotlin:kotlin-stdlib:{strictly 2.3.20}' because of: Dependency version enforced by Dependency Locking Could not resolve io.ktor:ktor-client-core:3.4.3. Constraint path: ... 'io.ktor:ktor-client-core:{strictly 3.4.2}' ... Regenerated via: cd core && ./gradlew --write-locks build Bare `./gradlew --write-locks` only rewrites buildscript-classpath locks (it runs :help and resolves nothing else); pairing with `build` forces resolution of every compile/runtime/test classpath in every subproject, which is what produces the diff CI needs. Verified: ./gradlew build → BUILD SUCCESSFUL in 2m 5s, 170 tasks, all locks now consistent with libs.versions.toml versions.
gkrost
added a commit
that referenced
this pull request
Jun 4, 2026
…-artefacts Fourth of six plans (the original P4 split into P4a + P4b to keep each plan reviewable). Creates the new unidrive-dist GitHub repo with its scaffolding (LICENSE, AGENTS.md with version-exception clause, BACKLOG, CLOSED, RELEASES, README, docs/), the tarball packaging channel, the fetch-artefacts.sh script (spec §3.4 tag regex + sibling GH-Release resolution), and the local-build.sh dev-loop driver. Spec: docs/dev/specs/unidrive-distribution-design.md §2.2, §3.3, §3.4, §4.1, §4.7, §6, §6.1, §10 AC #3.
gkrost
added a commit
that referenced
this pull request
Jun 4, 2026
* docs(spec): distribution & release engineering design Specifies how UniDrive ships to end users on Linux: a third repo (unidrive-dist) handles packaging, signing, and publishing; the existing unidrive and unidrive-mount-linux repos only publish their own raw artefacts on tag. Four MVP channels: tarball + apt + dnf + AUR. Snap/Flatpak deferred with explicit rationale. krost-infra gains a pkg-server container serving apt.unidrive.krost.org and dnf.unidrive.krost.org. Brainstormed and approved; awaiting implementation plan. * docs(spec): address review findings on distribution design Incorporates the review at docs/dev/reviews/unidrive-distribution-design-review.md plus the prior round of review notes: - §3.3 drop forced lockstep tagging; sibling repos tag only when their own code changes; unidrive-dist tag is authoritative; fetch-artefacts.sh queries latest matching SemVer GH Release. - §3.4 spell out the v0.0.1[-pkgN] tag-parsing regex; remove "trivial" hand-wave. - §4.2 fix invalid `systemctl --global daemon-reload` in deb postinst (and rpm %post); systemd auto-discovers user units, no daemon-reload needed. - §4.2 fix invalid `java21-runtime` virtual package dependency; use `java-runtime-headless (>= 21)`. - §4.2 add JDK shelf-life note: MVP pins to JDK 21; --enable-native-access flag form changes in 22+. - §4.3 add sourced verification that RHEL 10 ships kernel 6.12 (above the 6.9 floor). - §4.7 add changelog strategy: single RELEASES.md as source of truth, build-time render into debian/changelog and rpm %changelog. - §5 replace ambiguous in-CI signing with dedicated pkg-signer container on krost-infra; signing key never reaches the GH Actions runner. - §6 add RELEASES.md to repo layout. - §7.3.1 add unidrive.repo contents with repo_gpgcheck=1 and gpgkey=. - §7.4 change A records to CNAMEs targeting unidrive.krost.org so server-IP changes update one record, not three. - §7.5 rewrite SSH deploy account section; add deploy-key rotation playbook matching the GPG-key rotation in §3.7. - §8.2 ubuntu:24.04 (LTS, exists today) is primary smoke target; 26.04 added when GA. AUR smoke test creates non-root build user with sudo for pacman because makepkg refuses to run as root. - §10 AC #7 uses Ubuntu 24.04 LTS for first-release E2E smoke. - §4.4 AUR push uses a dedicated bot Arch account (unidrive-bot) registered on aur.archlinux.org; deploy keys aren't supported at the repo level on AUR. - §4.1, §4.2 JAR naming aligns with existing build output convention (unidrive-X.Y.Z.jar, not unidrive-cli-X.Y.Z.jar). - §4.1 tarball install.sh dynamically generates wrapper script with the versioned JAR path baked in. - §9 drop man page from MVP; CLI --help is canonical. - §9 replace "remote signing service" deferred item with "hardware-backed signing key (HSM/YubiKey)" since on-server signing container is now MVP. Also captures the review under docs/dev/reviews/ alongside the spec for posterity. * docs(spec): fold in second-review minor clarifications Second review (docs/dev/reviews/unidrive-distribution-design-review-2.md) confirmed no blocking issues. Folding in three of its six observations as spec-level clarifications: - §4.7: name the maintainer identity for debian/changelog and rpm %changelog headers (UniDrive Releases <releases@unidrive.krost.org>, matching the GPG identity from §5). - §5.2: explicitly list SHA256SUMS (tarball bundle), apt Release/InRelease, and dnf repomd.xml in the set of artefacts pushed to pkg-signer; remove ambiguity about what gets signed. - §8.4: note that the E2E manual smoke is interactive by design (unidrive auth opens a real OAuth flow); no headless equivalent for MVP. Three other observations from the review are deferred to writing-plans: pkg-signer stdin-vs-drop-dir choice (§5.1), sign-packages.sh local vs production role (§6, §8.5), Snap re-evaluation angle (§4.5; flagged by reviewer as design-continuity awareness only). * docs(plan): P1 — JVM release-workflow implementation plan First of five plans implementing the distribution spec. Adds a tag-triggered GH Actions workflow to unidrive that publishes the signed CLI fat JAR to GH Releases on v* tag push. Bite-sized tasks; full code blocks; local dry-run verifies the bash logic before the workflow ever fires. Spec: docs/dev/specs/unidrive-distribution-design.md §3.3 step 1, §4.1, §5, §10 AC #1. * docs(plan): P2 — Rust release-workflow plan for unidrive-mount-linux Second of five plans. Tag-triggered GH Actions workflow that cross-builds unidrive-mount for x86_64 and aarch64 (latter via cross-rs/cross), packages each as a tarball with LICENSE+NOTICE, signs and attaches to a GitHub Release. The plan describes work in the sibling unidrive-mount-linux repo but the plan file lives here because unidrive-mount-linux's AGENTS.md "Doc surface is bounded" rule does not sanction a docs/plans/ path, while this repo's AGENTS.md does. Also bumps unidrive-mount/Cargo.toml version 0.1.0 → 0.0.1 to align with the coordinated MVP release version per spec §10 AC #2. Spec: docs/dev/specs/unidrive-distribution-design.md §3.3 step 2, §4.1, §5, §10 AC #2. * docs(plan): P3 — krost-infra pkg-server + pkg-signer Third of five plans. Provisions the krost-infra side of the distribution stack: two new Docker Compose services (pkg-server static nginx for apt + dnf sub-domains; pkg-signer SSH-keyed signing service), Traefik routes, DNS CNAMEs, restricted SSH deploy users, GPG key generation on the VPS, GH Actions secrets provisioning, and the krost-infra docs sync required by its AGENTS.md. Plan lives in unidrive/docs/dev/plans/ (rather than krost-infra) because the distribution-spec plans co-locate with the spec; krost- infra has no docs/plans/ convention. Spec: docs/dev/specs/unidrive-distribution-design.md §5, §7.1–§7.6. * docs(plan): P4a — unidrive-dist scaffolding + tarball channel + fetch-artefacts Fourth of six plans (the original P4 split into P4a + P4b to keep each plan reviewable). Creates the new unidrive-dist GitHub repo with its scaffolding (LICENSE, AGENTS.md with version-exception clause, BACKLOG, CLOSED, RELEASES, README, docs/), the tarball packaging channel, the fetch-artefacts.sh script (spec §3.4 tag regex + sibling GH-Release resolution), and the local-build.sh dev-loop driver. Spec: docs/dev/specs/unidrive-distribution-design.md §2.2, §3.3, §3.4, §4.1, §4.7, §6, §6.1, §10 AC #3. * docs(plans): address review-3 findings on plans P1-P4a Six findings from the third review (now captured at docs/dev/reviews/unidrive-distribution-plans-review.md). Applied inline across the four affected plans: - P1: rewrote "no BuildInfo changes" scope clause to make the tension with spec §3.5 explicit; reconciliation deferred to P5 pre-flight rather than silently violating the spec at first tag. - P2: added KNOWN RISK comment in the workflow YAML noting two fallback strategies for cross 0.2.5 + edition 2024 incompatibility, and a new Task 4a that runs a real local aarch64 cross-build before the first tag push. - P3: added recovery-path comment to pkg-signer's sign-drop forced-command (sftp-pull retry, not re-sign). - P4a: documented version-extraction fragility for the awk-based parsing of core/build.gradle.kts; added gh-CLI auth prerequisite to fetch-artefacts.sh header; carved out the dev-loop exception in AGENTS.md's "no source code" rule. All six findings were minor-to-medium; none blocked the planning phase. P4b and P5 remain to be drafted. * docs(plan): P4b — unidrive-dist channels + orchestration + smoke matrix Fifth and sixth plans (P4b split into two files for output-token reasons; both halves implement one logical plan). Part 1 (Tasks 0-7): deb + rpm + AUR channel recipes, render-changelog shared by all three, extension of local-build.sh to cover deb/rpm/AUR, and sign-packages.sh (sftp to pkg-signer via ProxyJump, sign-drop, sftp back). Part 2 (Tasks 8-17): publish-apt / publish-dnf / publish-aur / publish-gh-release / release.sh top-level orchestrator, repo-server skeleton, Docker smoke matrix (ubuntu:24.04 / fedora:40 / archlinux:latest / debian:13), test-packaging.yml + release.yml CI workflows, AUR bot-account setup walkthrough. Spec: docs/dev/specs/unidrive-distribution-design.md §4.2, §4.3, §4.4, §4.6, §4.7, §5.1, §5.2, §7.3, §7.3.1, §8.1, §8.2, §8.6, §10 AC #4, #5, #6. P5 still to draft: first-release cutover (RELEASES.md content, real publish, AC verification, BuildInfo reconciliation from review-3 Issue 1, install landing page). * docs(plan): P5 — first-release cutover for v0.0.1 Sixth and final plan. Operator runbook for cutting the first real v0.0.1 UniDrive release. Touches all four working repos: - unidrive: fix(cli) reconciles BuildInfo --version output with spec §3.5 (review-3 Issue 1 resolution). - unidrive-mount-linux: tag v0.0.1. - unidrive-dist: first RELEASES.md entry, tag v0.0.1, fill in docs/release-process.md. - krost-infra: sites/unidrive/install/index.html landing page with per-channel install instructions and the GPG fingerprint. Includes: - AC #1-#8 verification map. - First AUR push + co-maintainer setup. - E2E manual smoke on Ubuntu 24.04 LTS per spec §8.4. - Common CI-failure recovery notes (cross 0.2.5 fallback, etc.). All six plans (P1, P2, P3, P4a, P4b, P5) now drafted on spec/distribution.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps org.xerial:sqlite-jdbc from 3.49.1.0 to 3.53.0.0.
Release notes
Sourced from org.xerial:sqlite-jdbc's releases.
... (truncated)
Commits
f88e9c7chore(release): 3.53.0.0 [skip ci]bdd2b64feat: publish multiple classifer jars7eb6f3ffeat: better Android support23ead2echore: update native librariesbaaf087feat(sqlite): upgrade to sqlite 3.53.0dd2adccfeat(jdbc): expose wal_autocheckpoint pragma in SQLiteConfigb649d25build(deps-dev): bump surefire.version from 3.5.4 to 3.5.5857a754build(deps-dev): bump org.assertj:assertj-core from 3.27.6 to 3.27.719259e5build(deps): bump org.sonatype.central:central-publishing-maven-plugina597952build(deps-dev): bump org.mockito:mockito-core from 5.21.0 to 5.23.0