Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions src/tooling/docs-assembler/assembler.yml
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,8 @@ references:
apm-aws-lambda:
apm-k8s-attacher:
beats:
current: "9.0"
next: main
Copy link

Choose a reason for hiding this comment

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

Can we have next as 9.1? That would ensure we don't publish main again by accident and that once v9.1.0 is released, there won't be any unreleased features in our docs.

Copy link
Contributor Author

@colleenmcginnis colleenmcginnis Jun 5, 2025

Choose a reason for hiding this comment

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

next only refers to which branch will be published to our internal staging site. There's no automation in place that will replace the current value with the next value.

As more repos start using different current / next branches (and as development in this repo continues), we'll likely replace the value of current with a variable like stack_version and the docs release manager will be responsible for updating the latest Stack version just like we did with AsciiDoc.

(@Mpdreamz please correct me if I got anything wrong!)

Copy link
Member

Choose a reason for hiding this comment

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

You didn't :)

cloud-on-k8s:
cloud:
current: master
Expand Down
Loading