Skip to content

Conversation

@beiske
Copy link
Member

@beiske beiske commented Apr 10, 2024

Release notes v1.13.0

Description

Related Issues

Motivation and Context

How Has This Been Tested?

Types of Changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Refactoring (improves code quality but has no user-facing effect)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation

Readiness Checklist

  • My code follows the code style of this project
  • My change requires a change to the documentation
  • I have updated the documentation accordingly
  • I have added tests to cover my changes
  • All new and existing tests passed
@beiske beiske requested review from a team and alaudazzi as code owners April 10, 2024 13:58
<titleabbrev>v1.13.0</titleabbrev>
++++

<<{p}-release-notes-v1.13.0-whats-new,What's new>> | <<{p}-release-notes-v1.13.0-bug-fixes,Bug fixes>> | <<{p}-release-notes-v1.13.0-breaking-changes,Breaking changes>> | <<{p}-release-notes-v1.13.0-changelog,Changelog>>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The docs build is failing because of this reference here to bugfixes which doesn't exist below.

@beiske beiske merged commit 7791a0d into elastic:master Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants