[mkurz]

Summary

This updates sbt-slick-codegen to cross-build and test on both sbt 1 and sbt 2, following the same migration pattern used in other sbt plugin repos.

It also replaces the old Docker-based CI/test setup with plain sbt-based GitHub Actions workflows and adds sbt-ci-release publishing.

Changes

• add plugin cross-build support for:
  • Scala 2.12.21 -> sbt 1.12.9
  • Scala 3.8.3 -> sbt 2.0.0-RC11
• add Scala 2 compatibility flag -Xsource:3
• fix sbt 2 task caching by marking slickCodegen as @transient
• update the scripted fixture so it passes on both sbt 1 and sbt 2
• replace the scripted test's external PostgreSQL dependency with in-process H2
• keep the scripted assertions and make the output path checks work with both sbt 1 and sbt 2 layouts
• replace the old ci.yml with build-test.yml in the same style as the other migrated repos
• add sbt-ci-release and a matching publish.yml
• remove obsolete Docker/Make/sbt-extras local test harness files

Notes

• The scripted test uses H2 instead of Docker/PostgreSQL so the new GitHub Actions workflow can run directly with sbt.

[mkurz]

@tototoshi ?

[tototoshi]

@mkurz
Thanks!
I think I've been inactive for about 2 years, but I'm ready to come back.

[mkurz]

I think I've been inactive for about 2 years, but I'm ready to come back.

@tototoshi If you want we can move this project to https://github.com/tototoshi/sbt-slick-codegen
What do you think?

[tototoshi]

@mkurz

If you want we can move this project to https://github.com/tototoshi/sbt-slick-codegen

Is the URL correct? 🤔

[mkurz]

Ah sorry typo, I meant
https://github.com/sbt/sbt-slick-codegen

[tototoshi]

@mkurz
That's great for me!

[mkurz]

@tototoshi can you

1. go to https://github.com/tototoshi/sbt-slick-codegen/settings
2. scroll down to "Transfer ownership" and click "Transfer"
3. choose "Specify an organization or username"
4. Enter eed3si9n (this is the sbt maintainer http://github.com/eed3si9n) and transfer the repo?

Eugene (eed3si9n) will then move the repo to the sbt organization.

Ping @eed3si9n just that you are aware a new repo coming in. Thanks!

[eed3si9n]

Yea, if anyone wants to move plugins to sbt org, just ping me like ☝🏼 and I'll move them to sbt with you and whoever else in the team.

[tototoshi]

@mkurz @eed3si9n
Thank you. I transferred the ownership.

[eed3si9n]

Transfer to sbt org is complete. I've created https://github.com/orgs/sbt/teams/sbt-slick-codegen-team team with Admin rights.

[eed3si9n]

It's up to you to keep com.github.tototoshi for publishing, or set up automated publishing for com.github.sbt.

[tototoshi]

I will change it to com.github.sbt.

[mkurz]

com.github.sbt

I have done that already in

• Adopt sbt-github-actions and com.github.sbt coordinates #107

😉

[mkurz]

made play samples use the latest snapshot, works!

• Latest sbt-slick-codegen snapshot now supports sbt2 playframework/play-samples#1590

[tototoshi]

Thank you!