Please add pgp credentials

[mkurz]

@ennru @johanandren can you please add your Lightbend PGP_SECRET and PGP_PASSPHRASE to the repository secrets?
Just like the ones you added to typesafe config: https://github.com/lightbend/config/actions/runs/17635897386/job/50111954258#step:5:56

gpg: key 36A22209606109DC: public key "Secure Bot <lightbend-tools-secure@lightbend.com>" imported
gpg: key 36A22209606109DC: secret key imported
gpg: Total number processed: 1
gpg:               imported: 1
gpg:       secret keys read: 1
gpg:   secret keys imported: 1

I already pushed out 3 milestone releases: https://repo1.maven.org/maven2/com/typesafe/ssl-config-core_2.13/ To do that I added our Play gpg credentials, but because this is your repo, I would prefer if you just add yours (in reality it does not really matter because sonatype does not check them - its just important things get signed).

After that I want to release version 0.7.0. Done.

• Everything passes for play-ws: Upgrade ssl-config + cleanup reference.conf + make TLSv1.3 default playframework/play-ws#1099
• all gigahorse tests pass locally for me, waiting for approvals on the PR: ssl-config-core 0.7.0 + upgrade Scala eed3si9n/gigahorse#104
• all scala-server-toolkit tests pass locally for me, waiting for approvals on the PR: ssl-config-core 0.7.0 + upgrade Scala and sbt-scalafix avast/scala-server-toolkit#1384

[mkurz]

To move on I released 0.7.0: https://github.com/lightbend/ssl-config/releases/tag/v0.7.0

@ennru @johanandren if you could still provide your own gpg key / passphrase that would be better I guess (I removed ours again).

[ennru]

Ok. I'll look into it.