Skip to content

Conversation

@AlexSkrypnyk
Copy link
Member

@AlexSkrypnyk AlexSkrypnyk commented Jul 26, 2025

Summary by CodeRabbit

  • Documentation

    • Added a new release notes template to standardize documenting changes between software versions.
    • Updated release process documentation to include a step for creating release notes using the new template.
  • Chores

    • Updated the documentation serve command to use a different script for local documentation preview.

@coderabbitai
Copy link

coderabbitai bot commented Jul 26, 2025

Walkthrough

The changes update the documentation and configuration for the release process. The docs-serve command in the configuration now uses the start script instead of serve. The release process documentation adds a step to create release notes using a newly introduced release template file, which provides a structured format and checklist for releases.

Changes

File(s) Summary
.vortex/.ahoy.yml Modified the docs-serve command to run the start script instead of serve.
.vortex/docs/content/contributing/maintenance/release.mdx Added a new step to the release process instructing creation of release notes using the provided template.
.vortex/docs/content/contributing/maintenance/release_template.md Added a new release notes template file with structured sections and a detailed release checklist.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Poem

🐇
A hop to "start" where "serve" once lay,
New notes to guide each release day.
With templates neat and checklists clear,
Our maintenance path is crystal here.
Docs refreshed, the process tight—
The vortex spins, all set right!

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feature/add-vortex-release-template

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot temporarily deployed to commit July 26, 2025 10:34 Inactive
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 3

🔭 Outside diff range comments (1)
.vortex/.ahoy.yml (1)

22-27: docs and docs-serve now execute the same command – semantic overlap
Changing docs-serve to yarn … start makes it identical to the docs target, losing the former distinction between development server vs serving the built static output. If the project still needs a command to serve the pre-built documentation (often yarn … serve), consider restoring it or renaming the commands to reflect their true purpose.

-      yarn --cwd=docs run start
+      # If the intent is to serve the already-built static files,
+      # keep using the dedicated `serve` script; otherwise drop the
+      # separate target to avoid duplication.
+      yarn --cwd=docs run serve
📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e636ae9 and 7a800d2.

📒 Files selected for processing (3)
  • .vortex/.ahoy.yml (1 hunks)
  • .vortex/docs/content/contributing/maintenance/release.mdx (1 hunks)
  • .vortex/docs/content/contributing/maintenance/release_template.md (1 hunks)
🧰 Additional context used
🧠 Learnings (2)
.vortex/docs/content/contributing/maintenance/release.mdx (1)

Learnt from: CR
PR: drevops/vortex#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T15:00:28.327Z
Learning: Node.js dependencies are updated in theme directories via RenovateBot

.vortex/docs/content/contributing/maintenance/release_template.md (3)

Learnt from: CR
PR: drevops/vortex#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T15:00:28.327Z
Learning: Composer dependencies are updated automatically with compatibility checks via RenovateBot

Learnt from: CR
PR: drevops/vortex#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T15:00:28.327Z
Learning: Docker images are updated for containers via RenovateBot

Learnt from: CR
PR: drevops/vortex#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T15:00:28.327Z
Learning: Node.js dependencies are updated in theme directories via RenovateBot

🪛 LanguageTool
.vortex/docs/content/contributing/maintenance/release_template.md

[grammar] ~1-~1: Use correct spacing
Context: ## What's new since [PREVIOUS_VERSION] [SHORT SUMMARY] ## Notable changes Non...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~3-~3: Use correct spacing
Context: ...'s new since [PREVIOUS_VERSION] [SHORT SUMMARY] ## Notable changes None --- ## 💥 Breaki...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~5-~5: Use correct spacing
Context: ...S_VERSION] [SHORT SUMMARY] ## Notable changes None --- ## 💥 Breaking changes None ...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~11-~11: Use correct spacing
Context: ...able changes None --- ## 💥 Breaking changes None --- ## 💧 Drupal ### New feature...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~17-~17: Use correct spacing
Context: ...# 💥 Breaking changes None --- ## 💧 Drupal ### New features None ### Fixes None ###...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~19-~19: Use correct spacing
Context: ...anges None --- ## 💧 Drupal ### New features None ### Fixes None ### Updates None...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~23-~23: Use correct spacing
Context: ... 💧 Drupal ### New features None ### Fixes None ### Updates None ## ☁️ Hosting ...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~27-~27: Use correct spacing
Context: ...ew features None ### Fixes None ### Updates None ## ☁️ Hosting ### New features ...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~32-~32: Use correct spacing
Context: ... Fixes None ### Updates None ## ☁️ Hosting ### New features None ### Fixes None ###...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~34-~34: Use correct spacing
Context: ... Updates None ## ☁️ Hosting ### New features None ### Fixes None ### Updates None...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~38-~38: Use correct spacing
Context: ...☁️ Hosting ### New features None ### Fixes None ### Updates None ## 🏗 Continuo...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~42-~42: Use correct spacing
Context: ...ew features None ### Fixes None ### Updates None ## 🏗 Continuous Integration ###...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~47-~47: Use correct spacing
Context: ...e ### Updates None ## 🏗 Continuous Integration ### New features None ### Fixes None ###...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~49-~49: Use correct spacing
Context: ... ## 🏗 Continuous Integration ### New features None ### Fixes None ### Updates None...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~53-~53: Use correct spacing
Context: ...ntegration ### New features None ### Fixes None ### Updates None ## 💻 Local De...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~57-~57: Use correct spacing
Context: ...ew features None ### Fixes None ### Updates None ## 💻 Local Development and conta...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~62-~62: Use correct spacing
Context: ...es None ## 💻 Local Development and containers ### New features None ### Fixes None ###...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~64-~64: Use correct spacing
Context: ...cal Development and containers ### New features None ### Fixes None ### Updates None...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~68-~68: Use correct spacing
Context: ...containers ### New features None ### Fixes None ### Updates None ## 🛠️ Tools ...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~72-~72: Use correct spacing
Context: ...ew features None ### Fixes None ### Updates None ## 🛠️ Tools ### New features N...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~77-~77: Use correct spacing
Context: ...Fixes None ### Updates None ## 🛠️ Tools ### New features None ### Fixes None ###...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~79-~79: Use correct spacing
Context: ...# Updates None ## 🛠️ Tools ### New features None ### Fixes None ### Updates None...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~83-~83: Use correct spacing
Context: ... 🛠️ Tools ### New features None ### Fixes None ### Updates None ## ⚙️ Workflow...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~87-~87: Use correct spacing
Context: ...ew features None ### Fixes None ### Updates None ## ⚙️ Workflow ### New features ...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~92-~92: Use correct spacing
Context: ... Fixes None ### Updates None ## ⚙️ Workflow ### New features None ### Fixes None ###...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~94-~94: Use correct spacing
Context: ...Updates None ## ⚙️ Workflow ### New features None ### Fixes None ### Updates None...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~98-~98: Use correct spacing
Context: ...️ Workflow ### New features None ### Fixes None ### Updates None ## 🌀 Vortex ...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~102-~102: Use correct spacing
Context: ...ew features None ### Fixes None ### Updates None ## 🌀 Vortex - 📖 Documentation:...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~107-~107: Use correct spacing
Context: ... Fixes None ### Updates None ## 🌀 Vortex - 📖 Documentation: - - 🎛️ Installer: ...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~109-~109: There might be a mistake here.
Context: ... ### Updates None ## 🌀 Vortex - 📖 Documentation: - - 🎛️ Installer: - - 🔧 Vortex mainte...

(QB_NEW_EN_OTHER)


[grammar] ~112-~112: There might be a mistake here.
Context: ... Vortex - 📖 Documentation: - - 🎛️ Installer: - - 🔧 Vortex maintenance: - --- ## 📋...

(QB_NEW_EN_OTHER)


[grammar] ~115-~115: There might be a mistake here.
Context: ... - - 🎛️ Installer: - - 🔧 Vortex maintenance: - --- ## 📋 Release checklist - [ ] Updated ...

(QB_NEW_EN_OTHER)


[grammar] ~120-~120: Use correct spacing
Context: ...ex maintenance: - --- ## 📋 Release checklist - [ ] Updated all dependencies outside of ...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[style] ~122-~122: This phrase is redundant. Consider using “outside”.
Context: ...ecklist - [ ] Updated all dependencies outside of the schedule - [ ] Updated container im...

(OUTSIDE_OF)


[grammar] ~122-~122: There might be a mistake here.
Context: ...Updated all dependencies outside of the schedule - [ ] Updated container images to the late...

(QB_NEW_EN_OTHER)


[grammar] ~123-~123: There might be a mistake here.
Context: ...latest versions and checked that @see links - [ ] Updated PHP version in `composer.jso...

(QB_NEW_EN_OTHER)


[grammar] ~130-~130: Use correct spacing
Context: ...s/build-test-deploy.yml`. - [ ] Updated documentation. --- Full Changelog: https://github.com/dre...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~134-~134: There might be a problem here.
Context: ...ocumentation. --- Full Changelog: [PREVIOUS_VERSION]...[NEW_VERSION] @AlexSkrypnyk, @renovate[bot] and [renovate[bot]](https://github.com/apps...

(QB_NEW_EN_MERGED_MATCH)

🪛 markdownlint-cli2 (0.17.2)
.vortex/docs/content/contributing/maintenance/release_template.md

1-1: First line in a file should be a top-level heading

(MD041, first-line-heading, first-line-h1)


31-31: Multiple consecutive blank lines
Expected: 1; Actual: 2

(MD012, no-multiple-blanks)


46-46: Multiple consecutive blank lines
Expected: 1; Actual: 2

(MD012, no-multiple-blanks)


61-61: Multiple consecutive blank lines
Expected: 1; Actual: 2

(MD012, no-multiple-blanks)


76-76: Multiple consecutive blank lines
Expected: 1; Actual: 2

(MD012, no-multiple-blanks)


91-91: Multiple consecutive blank lines
Expected: 1; Actual: 2

(MD012, no-multiple-blanks)


106-106: Multiple consecutive blank lines
Expected: 1; Actual: 2

(MD012, no-multiple-blanks)


109-109: Heading style
Expected: atx; Actual: setext

(MD003, heading-style)


109-109: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)


112-112: Heading style
Expected: atx; Actual: setext

(MD003, heading-style)


112-112: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)


115-115: Heading style
Expected: atx; Actual: setext

(MD003, heading-style)


115-115: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)


134-134: Bare URL used

(MD034, no-bare-urls)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (13)
  • GitHub Check: build (1)
  • GitHub Check: build (0)
  • GitHub Check: vortex-test-deployment (1)
  • GitHub Check: vortex-test-deployment (0)
  • GitHub Check: vortex-test-workflow (3)
  • GitHub Check: vortex-test-workflow (0)
  • GitHub Check: vortex-test-workflow (2)
  • GitHub Check: vortex-test-workflow (1)
  • GitHub Check: vortex-test-common
  • GitHub Check: vortex-test-installer (8.4)
  • GitHub Check: vortex-test-installer (8.2)
  • GitHub Check: vortex-test-installer (8.3)
  • GitHub Check: vortex-test-docs
🔇 Additional comments (1)
.vortex/docs/content/contributing/maintenance/release.mdx (1)

17-18: Link path looks good – but verify render in doc site
The relative link to ./release_template.md should work once both files are in the same directory. Just confirm the MDX renderer keeps the .md extension intact.

Comment on lines +1 to +3
## What's new since [PREVIOUS_VERSION]

[SHORT SUMMARY]
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Add a mandatory H1 heading before any other content
Markdown-lint (MD041) fails because the file does not start with a top-level heading. This will break the docs build in CI.

+# Release [NEW_VERSION]
+
 ## What's new since [PREVIOUS_VERSION]
 [SHORT SUMMARY]
📝 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
## What's new since [PREVIOUS_VERSION]
[SHORT SUMMARY]
# Release [NEW_VERSION]
## What's new since [PREVIOUS_VERSION]
[SHORT SUMMARY]
🧰 Tools
🪛 LanguageTool

[grammar] ~1-~1: Use correct spacing
Context: ## What's new since [PREVIOUS_VERSION] [SHORT SUMMARY] ## Notable changes Non...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~3-~3: Use correct spacing
Context: ...'s new since [PREVIOUS_VERSION] [SHORT SUMMARY] ## Notable changes None --- ## 💥 Breaki...

(QB_NEW_EN_OTHER_ERROR_IDS_5)

🪛 markdownlint-cli2 (0.17.2)

1-1: First line in a file should be a top-level heading

(MD041, first-line-heading, first-line-h1)

🤖 Prompt for AI Agents
In .vortex/docs/content/contributing/maintenance/release_template.md at lines 1
to 3, add a mandatory top-level heading (H1) as the very first line of the file
before any other content to satisfy markdown-lint MD041 and prevent CI build
failures.

Comment on lines +120 to +124
## 📋 Release checklist

- [ ] Updated all dependencies outside of the schedule
- [ ] Updated container images to the latest versions and checked that `@see` links
- [ ] Updated PHP version in `composer.json` for `config.platform`.
Copy link

Choose a reason for hiding this comment

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

🧹 Nitpick (assertive)

Tighten wording in checklist item
“outside of the schedule” is redundant and flagged by GrammarTool.

-- [ ] Updated all dependencies outside of the schedule
+- [ ] Updated all dependencies outside the schedule
📝 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
## 📋 Release checklist
- [ ] Updated all dependencies outside of the schedule
- [ ] Updated container images to the latest versions and checked that `@see` links
- [ ] Updated PHP version in `composer.json` for `config.platform`.
## 📋 Release checklist
- [ ] Updated all dependencies outside the schedule
- [ ] Updated container images to the latest versions and checked that `@see` links
- [ ] Updated PHP version in `composer.json` for `config.platform`.
🧰 Tools
🪛 LanguageTool

[grammar] ~120-~120: Use correct spacing
Context: ...ex maintenance: - --- ## 📋 Release checklist - [ ] Updated all dependencies outside of ...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[style] ~122-~122: This phrase is redundant. Consider using “outside”.
Context: ...ecklist - [ ] Updated all dependencies outside of the schedule - [ ] Updated container im...

(OUTSIDE_OF)


[grammar] ~122-~122: There might be a mistake here.
Context: ...Updated all dependencies outside of the schedule - [ ] Updated container images to the late...

(QB_NEW_EN_OTHER)


[grammar] ~123-~123: There might be a mistake here.
Context: ...latest versions and checked that @see links - [ ] Updated PHP version in `composer.jso...

(QB_NEW_EN_OTHER)

🤖 Prompt for AI Agents
In .vortex/docs/content/contributing/maintenance/release_template.md around
lines 120 to 124, the phrase "outside of the schedule" in the checklist item is
redundant. Simplify the wording by removing "outside of the schedule" to make
the checklist clearer and more concise.

Comment on lines +134 to +135
**Full Changelog**: https://github.com/drevops/vortex/compare/[PREVIOUS_VERSION]...[NEW_VERSION]

Copy link

Choose a reason for hiding this comment

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

🧹 Nitpick (assertive)

Avoid bare URL – convert to a proper Markdown link
MD034 reports a violation; using an explicit link improves readability.

-**Full Changelog**: https://github.com/drevops/vortex/compare/[PREVIOUS_VERSION]...[NEW_VERSION]
+**Full Changelog**: [Compare changes](https://github.com/drevops/vortex/compare/[PREVIOUS_VERSION]...[NEW_VERSION])
📝 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
**Full Changelog**: https://github.com/drevops/vortex/compare/[PREVIOUS_VERSION]...[NEW_VERSION]
**Full Changelog**: [Compare changes](https://github.com/drevops/vortex/compare/[PREVIOUS_VERSION]...[NEW_VERSION])
🧰 Tools
🪛 LanguageTool

[grammar] ~134-~134: There might be a problem here.
Context: ...ocumentation. --- Full Changelog: [PREVIOUS_VERSION]...[NEW_VERSION] @AlexSkrypnyk, @renovate[bot] and [renovate[bot]](https://github.com/apps...

(QB_NEW_EN_MERGED_MATCH)

🪛 markdownlint-cli2 (0.17.2)

134-134: Bare URL used

(MD034, no-bare-urls)

🤖 Prompt for AI Agents
In .vortex/docs/content/contributing/maintenance/release_template.md at lines
134 to 135, the full changelog URL is presented as a bare URL which violates
MD034. Replace the bare URL with a proper Markdown link by enclosing the link
text in brackets and the URL in parentheses, for example, use [Full
Changelog](https://github.com/drevops/vortex/compare/[PREVIOUS_VERSION]...[NEW_VERSION])
to improve readability and comply with Markdown standards.

@codecov
Copy link

codecov bot commented Jul 26, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.22%. Comparing base (e636ae9) to head (7a800d2).

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1851      +/-   ##
===========================================
+ Coverage    74.57%   75.22%   +0.65%     
===========================================
  Files           78       84       +6     
  Lines         4735     4860     +125     
  Branches         0       35      +35     
===========================================
+ Hits          3531     3656     +125     
  Misses        1204     1204              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@AlexSkrypnyk AlexSkrypnyk merged commit a9ed696 into develop Jul 26, 2025
30 checks passed
@AlexSkrypnyk AlexSkrypnyk deleted the feature/add-vortex-release-template branch July 26, 2025 11:14
@github-project-automation github-project-automation bot moved this from BACKLOG to Release queue in Vortex Jul 26, 2025
@AlexSkrypnyk AlexSkrypnyk moved this from Release queue to Released in 25.7.0 in Vortex Jul 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

2 participants