v0.93.0-rc2

What's Changed

• chore: PC-15033 Remove triggeredBySLOCreation and Edit by @marcinlawnik in #609
• fix: Fix budget adjustments e2e tests by @kubaceg in #611

Full Changelog: v0.93.0-rc1...v0.93.0-rc2

v0.92.3

What's Changed

🐞 Bug Fixes

• fix: Fix budget adjustments e2e tests (#611) @kubaceg

v0.93.0-rc1

What's Changed

• fix: PC-15140 Add at least second time resolution for firstEventStart field by @kubaceg in #608

Full Changelog: v0.92.1...v0.93.0-rc1

v0.92.2

What's Changed

💻 Fixed Vulnerabilities

• chore: Update module golang.org/x/crypto to v0.31.0 [SECURITY] (#610) @renovate

🐞 Bug Fixes

• fix: PC-15140 Add at least second time resolution for firstEventStart field (#608) @kubaceg

🧰 Maintenance

• chore: PC-15033 Remove triggeredBySLOCreation and Edit (#609) @marcinlawnik
• chore: Update module golang.org/x/crypto to v0.31.0 [SECURITY] (#610) @renovate

v0.92.1

What's Changed

🐞 Bug Fixes

• fix: E2E tests are failing for composite SLOs (#606) @ditrytus

v0.92.0

What's Changed

🚀 Features

• feat: PC-13893 Deprecate usage of objective's value field for Composite SLOs (#549) @ditrytus

  Usage of spec.objective[0].value field for Composite SLOs becomes
  deprecated.

  • New Composite SLOs should not set value field.
  • New Composite SLOs will still accept value: 0 for backward
    compatibility with older versions of Nobl9 SDK and Nobl9 Terrafrom
    Provider.
  • If value was previously set to 0 for Composite SLO then it should
    be omitted going forward.
  • If value was previously set in Composite SLO to a number other than
    0 then it can no longer be updated but still will be accepted for
    backward compatibility.
    The usage of value for SLOs using ratio or threshold SLIs does not
    change.

🧰 Maintenance

• chore: Update golangci linter config (#603) @nieomylnieja
• chore: Update module golang.org/x/tools/cmd/goimports to v0.28.0 (#604) @renovate

v0.92.0-rc1

What's Changed

• chore: Update module golang.org/x/tools/cmd/goimports to v0.28.0 by @renovate in #604
• chore: Update golangci linter config by @nieomylnieja in #603
• feat: PC-13893 Deprecate usage of objective's value field for Composite SLOs by @ditrytus in #549

Full Changelog: v0.91.1...v0.92.0-rc1

v0.91.1

What's Changed

🐞 Bug Fixes

• fix: Fixed e2e tests after removing AlertMethod.Status (#602) @nobl9-adam-szymanski

v0.91.0

What's Changed

⚠️ Breaking Changes

• chore: Remove Status from kind AlertMethod (#595) @nobl9-adam-szymanski
• chore: Remove deprecated Body and Subject from Email alert method (#596) @nobl9-adam-szymanski

🚀 Features

• feat: PC-14959 Extend kind SLO with QueryValidationStatus (#598) @lukasz-dobek

  Add QueryValidationStatus definition to kind SLO status field.

• feat: Update Honeycomb config to support only single query good over total [PC-14879] (#591) @nieomylnieja

  Added spec.objectives[*].goodTotal.honeycomb single query count
  metrics support for Honeycomb SLOs.
  This configuration only supports attribute property and does not
  support calculation property.

🧰 Maintenance

5 changes

• chore: Remove Status from kind AlertMethod (#595) @nobl9-adam-szymanski
• chore: Add timeout to e2e-tests.yml (#601) @nieomylnieja
• chore: Update dependency cspell to v8.16.1 (#600) @renovate
• chore: Remove deprecated Body and Subject from Email alert method (#596) @nobl9-adam-szymanski
• chore: Correct bad/total SLO examples generation (#599) @nieomylnieja

v0.91.0-rc4

What's Changed

• feat: PC-14959 Extend kind SLO with QueryValidationStatus by @lukasz-dobek in #598

Full Changelog: v0.91.0-rc3...v0.91.0-rc4