• #24 Use JDK HTTP client when available, supporting versions without the apache httpclient library (1.21.11+)

• Support for NeoForge 1.20.6 and above
• Update the default config to be more sensible
• Remove references to "Mojang" accounts in the branding
• Enable reproducible builds

• Fix having to reauthenticate with OAuth very frequently. After installing this update you will need to reauthenticate once then shouldn't need to reauthenticate again for a long time. (dc6641f)
• Support NeoForge

Artifacts are available below and on the maven repo, as always.

Fixes an issue with forge-latest publishing that resulted in NoClassDefFoundErrors on archloom.

Makes some changes to how DevAuth is published in order to improve behavior in some situations. No changes to functionality.

DevAuth now respects XDG_CONFIG_HOME on linux. Default config folder is now $XDG_CONFIG_HOME/devauth, defaulting to ~/.config/devauth. This is a breaking change, you must copy or recreate your config files if you use linux.

Operating systems other than linux have no changes and are not affected by this release.

This is a major update to DevAuth. No bugs were reported during the beta period but that doesn't mean there aren't any.

Changes:

• Microsoft auth rewrite. Should be much faster when refreshing tokens, the code is also much cleaner.
• New HTML OAuth redirect screen (not stolen from MediaMod)
• Better default config
• New default config options
  • DevAuth is now disabled by default, and is only enabled when devauth.enabled property is set or if defaultEnabled config property is set.
• Use gg.essential.loom for building all versions, hopefully resulting in faster and more consistent builds.
• Publish DevAuth to a maven repository for ease of use. See the details below.
• Better storage of Microsoft account tokens. Existing configuration will be lost so you will need to log into all accounts again.

Maven Dependency

The details of how to add DevAuth as a maven dependency are in the readme. Because of the changes to defaults, if someone does not explictly enable DevAuth, it will do nothing, so it is safe to add a maven dependency to DevAuth even in large projects with many contributors. I will reiterate the important note that if you are using gg.essential.loom with the forge-legacy module, you must upgrade to version 0.10.0.2 of gg.essential.loom.

Support and Bug Reports

If you need support, join my discord.
If you have a bug report, join my discord or make an issue.

Small patch to fix fabric jars being published on maven with the wrong classifier.

Release 1.0.0-beta.1

This is the first beta for DevAuth 1.0.0. There have been many changes, both internal and in the user facing parts of DevAuth, so please read this completely before updating.

Changes:

• Microsoft auth rewrite. Should be much faster when refreshing tokens, the code is also much cleaner.
• New HTML OAuth redirect screen (not stolen from MediaMod)
• Better default config
• New default config options
  • DevAuth is now disabled by default, and is only enabled when devauth.enabled property is set or if defaultEnabled config property is set.
• Use gg.essential.loom for building all versions, hopefully resulting in faster and more consistent builds.
• Publish DevAuth to a maven repository for ease of use. See the details below.

Maven Dependency

The details of how to add DevAuth as a maven dependency are in the readme. Because of the changes to defaults, if someone does not explictly enable DevAuth, it will do nothing, so it is safe to add a maven dependency to DevAuth even in large projects with many contributors. I will reiterate the important note that if you are using gg.essential.loom with the forge-legacy module, you must upgrade to version 0.10.0.2 of gg.essential.loom.

Support and Bug Reports

If you need support, join my discord.
If you have a bug report, join my discord or make an issue.

• added forge-latest (1.14 - 1.17.1) support