set up 8.9 dev cycle

[pzl]

Change Summary

Setup the 8.9 development cycle

-next convention is now reserved for use in the changelog file, as its intention is to relax the linter:

to allow the top-line changelog version to differ from the manifest version during development, where the manifest file version will likely change with each prerelease. Now the changelog version does not have to constantly change to match.

However, the manifest version does need to continually change to actually perform releases. We cannot overwrite a previous release (even prerelease) with the same version name. So we are going back to the -dev.N convention for now, incrementing periodically. This will likely be automated in the future

[elasticmachine]

💔 Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-04-26T13:57:45.327+0000

• Duration: 6 min 17 sec

Steps errors

Expand to view the steps failures

Update the Elastic stack

• Took 1 min 59 sec . View more details here
• Description: ./scripts/go-tools/bin/elastic-package stack update -v --version 8.9.0

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[pzl]

CI is just failing because 8.9 stack is not ready for pulling yet. This can merge without that (although that means all incoming PRs will fail until 8.9 stack container exists)