Skip to content
Open
Show file tree
Hide file tree
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
28 changes: 28 additions & 0 deletions assemblies/release-notes/assembly_mta-8-2-0.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
:_newdoc-version: 2.18.7
:_template-generated: 2026-06-12
:_mod-docs-content-type: ASSEMBLY

ifdef::context[:parent-context-of-mta-8-2-0: {context}]

ifndef::context[]
[id="mta-8-2-0"]
endif::[]
ifdef::context[]
[id="mta-8-2-0_{context}"]
endif::[]
= {ProductFirstRef} 8.2

:context: mta-8-2-0

[role="_abstract"]
Review new features, enhancements, Technology Preview features, removed features, fixed issues, and known issues in {ProductFullName} 8.2.0.
Comment on lines +17 to +18

@coderabbitai coderabbitai Bot Jun 12, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Trim the abstract to the included sections.

This abstract still advertises Technology Preview, removed features, and known-issues content, but this assembly only includes the new-features and fixed-issues topics. Either add the missing includes or narrow the abstract so the page doesn't promise sections that aren't present.

♻️ Proposed fix
-[role="_abstract"]
-Review new features, enhancements, Technology Preview features, removed features, fixed issues, and known issues in {ProductFullName} 8.2.0.
+[role="_abstract"]
+Review new features, enhancements, and fixed issues in {ProductFullName} 8.2.0.

Based on the existing 8.1.0 assembly pattern, the abstract should mirror the sections that are actually included.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
[role="_abstract"]
Review new features, enhancements, Technology Preview features, removed features, fixed issues, and known issues in {ProductFullName} 8.2.0.
[role="_abstract"]
Review new features, enhancements, and fixed issues in {ProductFullName} 8.2.0.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@assemblies/release-notes/assembly_mta-8-2-0.adoc` around lines 17 - 18, The
abstract currently promises sections not present; update the role="_abstract"
text in assembly_mta-8-2-0.adoc to only list the sections actually included
(new-features and fixed-issues). Edit the line that begins with
[role="_abstract"] / the following sentence so it references only
"{ProductFullName} 8.2.0 new features and fixed issues" (remove references to
Technology Preview, removed features, and known issues) to match the assembly
contents.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

AI: @mpershina, adjust when the RNs list is confirmed

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@mpershina, sounds good — I'll leave this as-is for now. Feel free to update the abstract once the final release notes list for 8.2.0 is confirmed.


🧠 Learnings used
Learnt from: Pkylas007
Repo: migtools/mta-documentation PR: 329
File: docs/topics/rules-development/yaml-provider-conditions.adoc:457-457
Timestamp: 2026-03-18T08:59:21.462Z
Learning: In migtools/mta-documentation, do not flag or review cross-reference (xref) anchor ID mismatches or broken xrefs in AsciiDoc (.adoc) files. Maintainers have explicitly requested ignoring xref issues for this repository. Apply this guidance to all .adoc files in the project (pattern: **/*.adoc); do not raise xref-related review comments for these files unless the directive is explicitly lifted.

Learnt from: Pkylas007
Repo: migtools/mta-documentation PR: 326
File: assemblies/ui-guide/assembly_centralized-configurations-analysis.adoc:20-20
Timestamp: 2026-03-30T15:14:19.266Z
Learning: In this repository’s AsciiDoc (.adoc) files, follow Red Hat documentation style for the specific construct: it’s acceptable to use a sentence fragment that starts with “For example, …” as a standalone sentence when it follows a preceding complete statement. Do not flag this as an AsciiDoc grammar or readability issue.

Learnt from: mpershina
Repo: migtools/mta-documentation PR: 339
File: docs/topics/vscode/proc_vscode-analyzing-application.adoc:6-6
Timestamp: 2026-04-09T08:49:54.549Z
Learning: In the documentation, when introducing an acronym/abbreviation, write the full expanded name first and then the abbreviation in parentheses. Example: "Remote Procedure Call (RPC)". Do not use the reverse order (e.g., "RPC (Remote Procedure Call)") when first defining the acronym.


include::topics/release-notes-topics/ref_new-features-and-enhancements-8-2-0.adoc[leveloffset=+1]

include::topics/release-notes-topics/ref_known-issues-8-2-0.adoc[leveloffset=+1]

include::topics/release-notes-topics/ref_fixed-issues-8-2-0.adoc[leveloffset=+1]

ifdef::parent-context-of-mta-8-2-0[:context: {parent-context-of-mta-8-2-0}]
ifndef::parent-context-of-mta-8-2-0[:!context:]

2 changes: 2 additions & 0 deletions docs/release-notes/master.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,8 @@ include::topics/templates/document-attributes.adoc[]
= Release Notes


include::assemblies/release-notes/assembly_mta-8-2-0.adoc[leveloffset=+1]

include::assemblies/release-notes/assembly_mta-8-1.adoc[leveloffset=+1]

include::assemblies/release-notes/assembly_mta-8-0.adoc[leveloffset=+1]
Expand Down
9 changes: 9 additions & 0 deletions docs/topics/release-notes-topics/ref_fixed-issues-8-2-0.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
:_newdoc-version: 2.18.7
:_template-generated: 2026-06-12
:_mod-docs-content-type: REFERENCE

[id="fixed-issues-8-2-0_{context}"]
= Fixed issues

[role="_abstract"]
Review issues that have been fixed in {ProductFirstRef} ({ProductShortName}) version 8.2.0.
13 changes: 13 additions & 0 deletions docs/topics/release-notes-topics/ref_known-issues-8-2-0.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
:_newdoc-version: 2.18.7
:_template-generated: 2026-07-01
:_mod-docs-content-type: REFERENCE

[id="known-issues-8-2-0_{context}"]
= Known issues

[role="_abstract"]
{ProductFirstRef} ({ProductShortName}) version 8.2.0 is affected by the following newly identified and previously known issues. A known issue is listed in all future release notes until resolved, at which point it is published as a fixed issue.

// placeholder for https://redhat.atlassian.net/browse/MTA-7103
// SME inputs: When running kubectl apply, if the namespace and its resources already exist on the target cluster, they will be silently overwritten. Since this is an issue with kubectl apply, it falls outside the scope of Crane.
Comment on lines +11 to +12

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

@istein1, could you please review this KI? Thanks a lot!

Suggested change
// placeholder for https://redhat.atlassian.net/browse/MTA-7103
// SME inputs: When running kubectl apply, if the namespace and its resources already exist on the target cluster, they will be silently overwritten. Since this is an issue with kubectl apply, it falls outside the scope of Crane.
Deploying mta-ops manifests overwrites existing target resources without warning::
+
The `mta-ops` pipeline lacks a pre-flight check to verify if a target namespace already exists. During deployment, the `kubectl apply` command silently overwrites existing resources by default without any warning. As a consequence, you might accidentally overwrite existing workloads on the target cluster.
+
To work around this problem, manually verify that the target namespace lacks conflicting resources before deployment.
+
link:https://redhat.atlassian.net/browse/MTA-7103[MTA-7103]


Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
:_newdoc-version: 2.18.7
:_template-generated: 2026-06-12
:_mod-docs-content-type: REFERENCE

[id="new-features-and-enhancements-8-2-0_{context}"]
= New features and enhancements

[role="_abstract"]
Review new features and enhancements in {ProductFirstRef} ({ProductShortName}) 8.2.0.


// main mta-ops RN placeholder (decide whether we need individual big feature RNs mentioned below or just a general one)



// MTA-6885 (multi-stage pipeline)



// MTA-6886 (cluster-level dependencies)



// MTA-6887 (validation)