boomshadow

# explicitly define host-ip mappings
# dnsmasq entries are always wildcard entries, so this maps both myapp.local and *.myapp.local
address=/myapp.local/219.219.219.125

# set the upstream resolver for people running Linux; this allows all other DNS to be resolved:
server=1.1.1.1
server=1.0.0.1

NAR8789

# explicitly define host-ip mappings
address=/myapp.local/172.16.1.2
# dnsmasq entries are always wildcard entries, so this maps both myapp.local and *.myapp.local

# (yes, it's fine for this to be your entire dnsmasq config. the defaults are pretty sensible)

sualeh

How to Sign and Release to The Central Repository with GitHub Actions

Warning

OSSRH Sunset: "As of June 30, 2025 OSSRH has reached end of life and has been shut down. All OSSRH namespaces have been migrated to Central Publisher Portal."

GitHub allows automated builds using GitHub Actions. A commonly asked question is how to release artifacts (packaged Java jars) built by Maven and Gradle to The Central Repository. The GitHub Actions documentation provides only part of the answer.

So, first, configure your Maven project for staging artifacts to The Central Repository, by reading through Configuring Your Project for Deployment and following those steps. Please make sure that the maven-gpg-plugin is configured to prevent gpg from using PIN entry programs, as follows:

<