Releases

Releases and versions

kcoap 0.1.0, the first release, came out on 6 November 2026, on Maven Central and GitHub Packages. It waited for the API-breaking work of the refactoring plan to land, so that it would not break its users right after.

  • Latest release0.1.0
  • Released6 November 2026
  • Release freeze13 of 13 merged
  • Published toMaven Central, GitHub Packages

On GitHub

Latest releases

Read live from GitHub when this page loads. Each release opens with the summary of its changelog entry, followed by the merged pull requests.

0.1.0, the first release

kcoap 0.1.0 came out on 6 November 2026. Its GitHub Release has the notes, and Get started shows how to add it from Maven Central.

The changelog lists every notable change by release, with a migration note for each breaking change; what changes after 0.1.0 goes under “Unreleased” until the next release.

Release freeze

What 0.1.0 waited for

No v* tag was pushed until thirteen work packages had merged: the ones that change the public API. All thirteen had merged on 6 November 2026, the day of the release:

  1. A1, merged
  2. A2, merged
  3. A3, merged
  4. A4, merged
  5. A5, merged
  6. W1, merged
  7. B1, merged
  8. B2, merged
  9. B3, merged
  10. C1, merged
  11. D1, merged
  12. D2, merged
  13. C3, merged
  • 13 merged
PackageWhat it doesState
A1OSCORE safe persistence and secret hygienemerged
A2EDHOC capability-aware negotiation, typed retry, returned sessionsmerged
A3The EDHOC and OSCORE glue on interfaces and the application modelmerged
A4kcoap-crypto as the home of shared crypto blocksmerged
A5DefaultCryptoBackend as a final adaptermerged
W1RFC 8323 transport follow-upsmerged
B1One internal link per peer under the CoAP endpointmerged
B2kcoap-coap-message split out of kcoap-coapmerged
B3The public API of kcoap-coap cleaned upmerged
C1Build governance: ABI dumps, common-only cores, opt-in markersmerged
D1Two configuration builders and explicit endpoint classesmerged
D2A KcoapException root, @Throws and a Swift smoke testmerged
C3Assembly and documentation: a BOM, a getting-started guide, a platforms guidemerged

TLS for stream transports (T1), browser interop (I1), a crypto conformance suite (C2), consumer samples (P1) and the rest of the CoAP errors and observability work (B4) merged too, but did not block the release. The freeze in the releasing guide.

Process

How a tag becomes a release

A release is a v* tag. The version is the tag without the v; between releases the build holds the next version with -SNAPSHOT.

  1. Test

    The whole CI workflow runs again: unit tests on every target, the coverage floor, interop with libcoap and libedhoc, the Apple targets and the API reference. Nothing is published if any of it fails.

  2. Publish

    A macOS runner builds every module for every target, signs each artifact with the release key 5833 7699 D9CB 8E6F 5EB1 BDFB 4A7E 4910 69FA EAB3, publishes them to GitHub Packages and uploads them to the Central Portal. The maintainer checks that deployment and publishes it to Maven Central by hand, a step that cannot be undone. The releasing guide says how to check a signature.

  3. Release notes

    A GitHub Release whose notes are the version’s summary from the changelog, followed by the merged pull requests. A version with a -, such as 0.2.0-rc1, is marked as a pre-release.

  4. API reference

    Dokka builds the reference and the workflow deploys it to GitHub Pages, at adihack.github.io/kcoap.

How a tag becomes a releasePushing a v* tag, such as v0.1.0, starts the release workflow. Step 1 runs the whole CI workflow; if any of it fails, nothing is published. Step 2 builds every module for every target on a macOS runner, signs each artifact with the release key, publishes them to GitHub Packages and uploads them to the Central Portal, where the maintainer publishes the deployment to Maven Central by hand. Step 3 creates the GitHub Release, whose notes are the version’s summary from the changelog followed by the merged pull requests. Step 4 deploys the API reference, built by Dokka, to GitHub Pages.A v* tag is pushedgit push origin v0.1.01 · Testthe whole CI workflow; nothing is published if it fails2 · Publish, on macOSevery module, every target, from one hostGitHub Packagesevery release, signedMaven Centralpublished by hand, signed3 · GitHub Releasethe changelog summary, then the merged pull requests4 · API referenceDokka, deployed to GitHub Pages
Read the diagram as text

Pushing a v* tag, such as v0.1.0, starts the release workflow. Step 1 runs the whole CI workflow; if any of it fails, nothing is published. Step 2 builds every module for every target on a macOS runner, signs each artifact with the release key, publishes them to GitHub Packages and uploads them to the Central Portal, where the maintainer publishes the deployment to Maven Central by hand. Step 3 creates the GitHub Release, whose notes are the version’s summary from the changelog followed by the merged pull requests. Step 4 deploys the API reference, built by Dokka, to GitHub Pages.

The release workflow, from tag to API reference.

Checklist

What 0.1.0 needed

The releasing guide’s checklist for the first release, as it stood after the release on 6 November 2026:

  • Done: The release freeze merged, pull request #1 brought it to main, and the whole CI workflow passed again on the tagged commit.
  • Done: Nothing deprecated is left in the API: the constructors of CoapEndpointConfig and CoapClientConfig, deprecated for their builders, are removed (work package P1).
  • Done: CHANGELOG.md has an entry for 0.1.0, with migration notes; its summary is the body of the GitHub Release.
  • Done: The dev.kcoap namespace is verified in Maven Central’s portal, through a DNS record on kcoap.dev, since 6 November 2026.
  • Done: The Maven Central user token and the release signing key are set as repository secrets, since 6 November 2026.
  • Done: Every POM names the license, the website, the maintainer, the issue tracker and the sources.
  • Done: Snapshots publish to Maven Local, kcoap-bom with them, which verifyBomConstraints checks against the published modules; CI builds an Android consumer app against them.
  • Done: A JVM consumer and a js consumer build against the snapshot through kcoap-bom, the js one within a bundle-size budget and in headless Chrome (work package P1); their CI jobs passed for the release.
  • Done: The ABI dumps are current: CI checked them again for the tag.
  • Done: A ruleset protects v* tags, and GitHub Pages serves from GitHub Actions.
  • Done: The Central Portal deployment is published: dev.kcoap:<module>:0.1.0 and kcoap-bom are on Maven Central.
  • Done: The API reference is online. Its first deploy from the tag failed, because the github-pages environment accepted deployments from main only; once it also allowed v* tags, the job ran again and deployed it.

Versioning

The versioning policy in short

Semantic Versioning 2.0.0, one version for every module, and a build that checks the public API on every change.

One version for all modules

Every published module is released at once with the same version. Use one version for all kcoap modules in a build: they share internal plumbing, and mixed versions are not supported.

Before 1.0

A minor release, such as 0.1.0 to 0.2.0, may break the API; each break is listed in the changelog under “Changed (breaking)” with a migration note. A patch release is fixes only and never breaks the API.

From 1.0

Breaking changes only in a major release, after a deprecation that lasts at least one minor release. A security fix that cannot avoid a break, or a raised minimum, may break in a minor.

API tiers

The stable API is what the ABI dumps hold. @ExperimentalKcoapApi may change in any minor release; @InternalKcoapApi is not API. Unpublished modules promise nothing.

On the wire

A deviation from an RFC is a bug, fixed in the next patch or minor. A default that changes the wire, such as turning Q-Block on, changes only in a minor or major release. Suite −24 follows its draft.

Security fixes

Listed under “Security” in the changelog. A behaviour change that removes a vulnerability may ship in a patch release.

Raising a minimum is a breaking change, in a minor or major release only.
MinimumVersion
AndroidAPI level 26 (Android 8.0)
Kotlin in a consuming project2.3 (kcoap is built with Kotlin 2.4)
JVM bytecode and runtimeJava 17
Building kcoapJDK 17

The full versioning policy · The releasing guide

Channels

Where releases are

Maven Central

Every release, under the verified dev.kcoap namespace: dev.kcoap:<module>:<version> from mavenCentral(), with no other repository. 0.1.0

GitHub Packages

Every release, from https://maven.pkg.github.com/adihack/kcoap. Gradle needs a GitHub token with read:packages to read it, even for a public package. 0.1.0

GitHub Releases

One per tag: the version’s summary from the changelog, then the merged pull requests. The artifacts are in the Maven repositories, not attached to the release. GitHub Releases.

API reference

Every release, at adihack.github.io/kcoap: every public declaration with its KDoc. ./gradlew dokkaGenerate in a clone of kcoap builds it into build/dokka/html. 0.1.0