Skip to content

Bump the parser from 4.1.11 to 4.2.6 - #51

Merged
sqlparser merged 1 commit into
masterfrom
bump-parser-4.2.6
Aug 24, 2026
Merged

Bump the parser from 4.1.11 to 4.2.6#51
sqlparser merged 1 commit into
masterfrom
bump-parser-4.2.6

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

4.2.6 is the newest release on sqlparser.com. Tonight's nightly ran it through the same checks the pinned 4.1.11 gets, and it passed all of them: the full test suite with no failures, every demo starting, and every case in .github/scripts/demo-cases.tsv producing its expected output.

This touches the four places the version is written -- pom.xml and the three connector/*/pom.xml -- via .github/scripts/set-parser-version.sh, so they cannot drift apart.

Merge to move the demos to 4.2.6. Close to stay on 4.1.11; the nightly will go on testing 4.2.6 and will not reopen this until a newer release appears.

Opened by nightly.yml.

The nightly ran the newest published release through the same checks
the pinned version gets, and it passed all of them:

  - full test suite, no failures
  - every demo starts
  - the demo cases in .github/scripts/demo-cases.tsv produce their
    expected output

Opened automatically by .github/workflows/nightly.yml. Merge it if you
want the demos on 4.2.6; close it to stay on 4.1.11, and the nightly
will keep testing 4.2.6 without asking again until a newer release
appears.
@sqlparser
sqlparser merged commit 7322fec into master Aug 24, 2026
3 checks passed
@sqlparser
sqlparser deleted the bump-parser-4.2.6 branch August 24, 2026 06:09
sqlparser added a commit that referenced this pull request Aug 24, 2026
…ry (#52)

nightly.yml opens the bump PR partly so that "the push-triggered build.yml
[gets] a chance to disagree". It does not get one. GitHub gates workflow runs
from first-time contributors -- this repository's policy is
`first_time_contributors`, read back from
/actions/permissions/fork-pr-contributor-approval -- and github-actions[bot]
counts as one, so the pull_request run on a bump branch is created in
`action_required` at 0s and never starts.

That is quiet in the worst way: `gh pr checks` reports "no checks reported",
which reads as "this workflow does not apply here" rather than "this workflow
is blocked". PR #51 (4.1.11 -> 4.2.6) sat like that and was only caught because
somebody happened to look. Merging in that state loses everything build.yml has
that the nightly does not already duplicate: the JDK 8 build, the pre-commit
hook test, and the whole windows-bat job.

So the `latest` job now finds that run and approves it. When the token cannot,
the notice goes on the PR itself rather than into a warning annotation on an
otherwise-green nightly, because that is the same kind of thing nobody reads.

Separately, both CLAUDE.md and the README said Gudu's Maven repo keeps only the
newest version and deletes the rest. Measured on 2026-08-24, it serves 4.1.9,
4.1.11 and 4.2.6 -- 200 for every .jar and .pom, and maven-metadata.xml lists
exactly those three, so the metadata is pruned in step rather than left stale.
4.1.11 went on resolving after 4.2.6 was published on 2026-08-23. The five
versions that did vanish on 2026-07-28 (4.1.4 through 4.1.8) are still 404 and
are not coming back, but that was a deliberate recall, not routine cleanup
after a release, and the README already documented it as such.


Claude-Session: https://claude.ai/code/session_01UK3dBXFXqiDRYJxz1YxWCr

Co-authored-by: James <James@gudusoft.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.

1 participant