chore(deps): bump github.com/mattn/go-sqlite3 from 1.14.28 to 1.14.44 in /QSDM/source#12
Open
dependabot[bot] wants to merge 1 commit into
Conversation
dependabot
Bot
added
dependencies
Owner
|
@dependabot rebase |
Bumps [github.com/mattn/go-sqlite3](https://github.com/mattn/go-sqlite3) from 1.14.28 to 1.14.44. - [Release notes](https://github.com/mattn/go-sqlite3/releases) - [Commits](mattn/go-sqlite3@v1.14.28...v1.14.44) --- updated-dependencies: - dependency-name: github.com/mattn/go-sqlite3 dependency-version: 1.14.44 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/go_modules/QSDM/source/github.com/mattn/go-sqlite3-1.14.44
branch
from
9782815 to
b1a972d
Compare
blackbeardONE
pushed a commit
that referenced
this pull request
May 11, 2026
…ld queue The macos-build.yml workflow had never actually completed a run end-to-end because the hosted macOS pool was queue-limited and concurrency.cancel-in-progress only cancels runs in the same head-ref group. 14h of backlog + 6 dependabot PRs sitting queued kept everything from ever reaching a runner. Cancelled 10 stale queued runs via the REST API (kept the latest v0.3.0 run). On the first run that actually got a runner, the no-CGO macos-14 job failed within 0.4s with: go: cannot find main module, but found .git/config in /Users/runner/work/QSDM/QSDM Root cause: build_macos.sh runs from working-directory=QSDM (the macos-build.yml convention), but go.mod lives at QSDM/source/go.mod. The CGO branch already handled the source/-indirection. The no-CGO branch did not -- it just called go build directly against the QSDM root, which has no go.mod. Fix: mirror the same `if [[ -f source/go.mod ]]; cd source` guard into the no-CGO branch. Also in this session: * Merged dependabot PR #11 (libp2p-pubsub 0.15.0 -> 0.16.0) after confirming all 24 PR-CI checks were green across build-test, govulncheck, trivy, docker, trustcheck, and wasm. * PR #12 (mattn/go-sqlite3 1.14.28 -> 1.14.44) hit a go.sum conflict after PR #11 merged -- triggered @dependabot rebase. * Posted @dependabot rebase on #1, #5, #6, #7, #8, #10 so they pick up the session-75 ripgrep fix and re-run cleanly. * Deferred PR #2 (login-action 3->4) and PR #13 (build-push-action 6->7): PR CI doesn't trigger release-container.yml (which runs only on push: tags: v*), so merging risks re-breaking the release pipeline we just stabilised in sessions 75-78. Path forward documented in RELEASE_NOTES_v0.3.0.md. Co-authored-by: Cursor <cursoragent@cursor.com>
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 github.com/mattn/go-sqlite3 from 1.14.28 to 1.14.44.
Commits
20826e8Merge pull request #1394 from mattn/sqlite-amalgamation-30530002d4d220fix changelog URL when minor or patch version is zero3761cf7Upgrade SQLite to version 30530001aa7317Merge pull request #1388 from mattn/stmt-cache-lruc719e20Merge pull request #1392 from mattn/fix-issue-1390-query-comment-panic869e516fix panic when querying input with no SQL (only comments/whitespace)6690238extract finalizeCachedStmt helper and drop redundant tail reset59e8e75only set stmt cacheKey when cache is enabled2badb4cuse slice len/cap for stmt cache instead of separate counters7716c20evict LRU stmt when stmt cache is full