Changelog

All notable user-visible changes are tracked here.

0.3.0

Adds the Bitbucket Cloud surface. Consume it with {:mvn/version "0.3.0"}.

Added

• Bitbucket: 316 functions across 14 namespaces covering the Bitbucket Cloud v2 REST API (api.bitbucket.org/2.0) — repositories, pull requests, commits, issues, pipelines, deployments, snippets, workspaces, projects, webhooks, refs (branches/tags/branch-restrictions/branching-model), source, users (SSH/GPG), and code search. Generated from the official OpenAPI spec and verified against it (method+path conformance 316/316, 1:1). Connect/app-only surfaces (addon, hosted properties) are intentionally omitted — they need app auth, not a user token.
• atlassian.bitbucket.client — a request seam over the single API root plus request-url/next-url helpers for Bitbucket's full-URL (:next) pagination.
• atlassian.config Bitbucket support: its own credentials (BITBUCKET_USERNAME + BITBUCKET_API_TOKEN, or an app password / Bearer token), independent of the Jira/Confluence vars.
• Every Bitbucket GET accepts an optional query opts map (fields, page, pagelen, q, sort).
• Static conformance tooling verify-spec-bitbucket and a live read-only Bitbucket sweep that self-skips when credentials are unset.

0.2.0

First published release to Clojars as net.clojars.deadmeme5441/atlassian-sdk. Consume it with {:mvn/version "0.2.0"}.

Added

• Jira: 575 functions across 24 namespaces covering the Jira Cloud Platform v3 API (every user-token-accessible endpoint), generated from the official OpenAPI spec and verified against it (method+path conformance 575/575, 1:1).
• Confluence: 334 functions across 22 namespaces covering both the modern v2 (/wiki/api/v2) and legacy v1 (/wiki/rest/api) surfaces, including CQL search; conformance 334/334, 1:1.
• HTTP core built on hato — no Apache HttpClient on the classpath. A single network seam (atlassian.client) under per-product request functions.
• Atlassian Document Format helpers (atlassian.jira.adf) and Confluence cursor pagination helper (atlassian.confluence.client/next-cursor).
• Unit test suite (no network) plus live read-only integration sweeps that self-skip when credentials are unset.
• Static conformance tooling (verify-spec, verify-spec-confluence, find-recursion) and a tag-driven Clojars release workflow: pushing a v* tag builds, tests, and deploys automatically.