Slick v4 migration - #1
Merged
Merged
Conversation
Add an explicit result type to the protected implicit `b1Type` (inferred slick.ast.TypedType[String]), as required by Scala 2.13's lint rules. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- organization: com.github.tminglei -> com.typesafe.slick; POM url/scm point to github.com/slick/slick-pg - version: open the Slick 4 series at 0.24.0, now derived from git tags via sbt-dynver (removed the hardcoded version) - release: adopt sbt-ci-release (matching slick/slick), set sonatypeProfileName := "com.typesafe.slick" - CI: modernize workflow (checkout@v6, setup-java@v5, sbt/setup-sbt@v1, fetch-depth 0 for dynver), fix Scala 3 matrix to 3.8.3, baseline Java at 17, add a tag-triggered `sbt ci-release` publish job - README: update dependency coordinates, version, and Slick version Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Update the README's source/test browsing links (and the issue link) from the upstream tminglei repo to the slick org fork. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Link to the official Scala Discord #slick channel, matching the badge used by the main slick/slick repo. The existing gitter link is kept. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…42.7.13 Update postgresql to 42.7.13
Update sbt, scripted-plugin to 1.12.15
….14.3 Update joda-time to 2.14.3
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
3 participants
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.
Remaining manual steps (not in this PR)
Required before the first release:
SONATYPE_USERNAME,SONATYPE_PASSWORD,PGP_SECRET(ASCII-armored private key),PGP_PASSPHRASE. Preferrably as org-level secrets.To cut the release (after the above):
master, then push av0.24.0tag.sbt-dynverturns the tag into version0.24.0and the tag-triggeredsbt ci-releasejob publishes to Maven Central. Nothing releases until this tag exists — pushing the branch/merging does not.