Repository navigation
docs: add v1.4.0-m.1 pre-release docs - #971
Merged
Merged
Conversation
Snapshot current docs as opt-in v1.4.0-m.1 version (non-default, noIndex, unreleased banner); keep v1.3.x as lastVersion. Signed-off-by: Rashad Sirajudeen <rashad@wso2.com>
Signed-off-by: Rashad Sirajudeen <rashad@wso2.com>
Contributor
|
No actionable comments were generated in the recent review.
 |
| Layer / File(s) | Summary |
|---|---|
Version configuration and release entry versions.json, docusaurus.config.ts, docs/changelog.md |
The version list and Docusaurus configuration add v1.4.0-m.1, with an unreleased banner and noIndex: true. The changelog records the release date and comparison link. |
Priority:
Estimated code review effort: 1 (Trivial) | ~3 minutes
Change: Other
Possibly related PRs
- openchoreo/openchoreo.github.io#968: Establishes v1.3.3 as the current v1.3.x release, which is the comparison baseline for this changelog entry.
Suggested reviewers: mirage20
Merge Risk: 
81433
-
The milestone documentation is registered without replacing the stable default. No concrete issue blocks merging after normal checks.
Pre-merge checks: 
-
Check name Status Explanation Title check The title clearly and concisely identifies the addition of v1.4.0-m.1 pre-release documentation. It matches the main changes. Description check The description clearly explains the purpose and implementation approach. It omits the template's Related Issues and Checklist sections, but it is otherwise sufficiently detailed and relevant. Docstring Coverage No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat… Linked Issues check Check skipped because no linked issues were found for this pull request. Out of Scope Changes check Check skipped because no linked issues were found for this pull request. Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 1 files. (2 skipped: 2 unsupported.)
-
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.
chathuranga95
approved these changes
Oct 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Snapshot docs for the v1.4.0-m.1 milestone pre-release, following the same pattern used for v1.2.0-m.1 and v1.3.0-rc.1.
Approach
npm run docusaurus docs:version v1.4.0-m.1to snapshot currentdocs/intoversioned_docs/version-v1.4.0-m.1/.docusaurus.config.tsas non-default, noIndex, with an "unreleased" banner —v1.3.xstayslastVersion._constants.mdxto the release branch's actual values (githubRef: release-v1.4.0-m.1,helmChart: 1.4.0-m.1, pinned observability module versions).v1.4.0-m.1row todocs/changelog.mdand the versioned snapshot'schangelog.md, linking to the GitHub compare view against the latest stable (v1.3.3).Keeping this PR open rather than merging immediately, per the release checklist.