Skip to main content

Service-Level objectives changelog

  • Changelog

@dynatrace-sdk/client-service-level-objectives

1.1.1 Released Oct 20, 2026​

Patch changes​

  • Published packages now include an exports map in their package.json (with types, require and import conditions), so Node.js resolves the esm/ output as native ES modules. Previously the module field was only honoured by bundlers, so the type: module marker in esm/package.json had no effect in plain Node.js ESM resolution. Deep imports into cjs/, esm/ or types/ that are not listed in the map are no longer permitted.

  • A package.json containing {"type":"module"} is now emitted into the esm/ output directory of each published package. This allows Node.js and bundlers to correctly identify the ESM output as ES modules without requiring the .mjs file extension.

  • Updated dependencies

  • Updated dependencies

  • Updated dependencies

  • Updated dependencies

  • Updated dependencies

  • Updated dependencies

    • @dynatrace-sdk/http-client@1.5.2
    • @dynatrace-sdk/shared-errors@1.1.0

1.1.0 Released Sep 10, 2026​

Minor changes​

  • Update JSDoc with example, minimum and default fields. (APPDEV-16816)

Patch changes​

  • Fix URL encoding of path parameters in generated API methods. Path segment values are now properly percent-encoded, preventing issues when IDs contain special characters. (APPDEV-19699, APPDEV-19700)
  • Generated TypeScript declarations are now rolled up into a single types/index.d.ts per entry point. (APPDEV-11700)
  • Update @dynatrace-sdk/http-client dependency.

1.0.0 Released Apr 29, 2026​

Major changes​

  • Add Service-Level Objectives SDK
Still have questions?
Find answers in the Dynatrace Community