Visitar URL original
Release 2026 05 lts by tikhanovichA · Pull Request #760 · oat-sa/tao-community · GitHub
Skip to content

Release 2026 05 lts - #760

Merged
tikhanovichA merged 9 commits into
masterfrom
release-2026-05-lts
May 8, 2026
Merged

tikhanovichA merged 9 commits into
masterfrom
release-2026-05-lts

Conversation

@tikhanovichA

@tikhanovichA tikhanovichA commented May 8, 2026 •

Copy link
Copy Markdown
Collaborator

Changelog

Comparing master → release-2026-05-lts (RC)

oat-sa/extension-tao-itemqti

Version: 32.3.1 → 32.4.2

Changes

  • Fix INF-475 : [] - feat: Added right space to all subcript styles #2975
  • Fix : add translations #2970
  • Fix AUT-4525 : : fix for svg rendering issues in authoring graphic interactions #2968
  • New Crowdin updates #2965
  • Fix AUT-4451 : [] : changeCallbacks selector fix for Include widget type. #2960

oat-sa/extension-tao-itemqti-pci

Version: 9.1.9 → 9.4.3

Changes

  • Fix INF-473 : : disable math entry symbols by default unless explicitly configured #489
  • Fix INF-484 : : fixed legacy Audio Recording interaction with using media stimulus #488
  • Fix INF-469 : [] : mathquill alignment with taoItemQti #496
  • Fix INF-464 : : legacy audio interaction PCI auto-playback #492
  • Feature INF-468 : preserve audio-recording PCI media stimulus playback limit #490
  • Fix INF-467 : : respect auto-recording limit #491
  • Fix INF-470 : : mathEntry creator latex postRender #487
  • Update translations from Crowdin #481
  • AUT-4499 : feat: enable response properties for IMS Audio Recording PCI #478
  • Fix TR-6783 : AudioRecording isDisabled check #476 ( by oatymart - validated by oatymart )
  • Fix : PCI manager layout #477 ( by oatymart - validated by oatymart )

oat-sa/extension-tao-testqti

Version: 50.1.5 → 50.2.1.1

Changes

oat-sa/tao-core

Version: 56.1.15 → 56.1.19

Changes

Full Changelog: oat-sa/tao-core@v56.1.18...v56.1.19

All Changes

  • Updated oat-sa/extension-tao-itemqti from 32.3.1 to 32.4.2
  • Updated oat-sa/extension-tao-itemqti-pci from 9.1.9 to 9.4.3
  • Updated oat-sa/extension-tao-testqti from 50.1.5 to 50.2.1.1
  • Updated oat-sa/tao-core from 56.1.15 to 56.1.19

Summary by CodeRabbit

  • Chores
    • Released 2026.05 LTS and bumped core platform and several extensions to newer patch/minor versions.
  • Tests
    • CI moved to Node.js 20 and expanded browser/runtime dependencies.
    • Front-end testing reworked: Puppeteer/Chromium environment configured, QUnit suites run per-suite, and a retry-capable runner added to reduce flakiness while preserving JUnit reporting.

@coderabbitai

coderabbitai Bot commented May 8, 2026 •

Copy link
Copy Markdown

Review Change Stack

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

Walkthrough

Updates composer.json release keyword and TAO dependency pins; sets CI Ubuntu job to Node.js 20, expands Chromium packages, centralizes Puppeteer/Chromium env vars, splits front-end Grunt tests into per-suite steps, and adds a retrying .github/scripts/run-fe-qunit.sh helper.

Changes

Dependency and Release Update

Layer / File(s) Summary
Release Keyword
composer.json
Release keyword updated from 2026.04 to 2026.05 LTS.
Dependency Version Pins
composer.json
oat-sa/tao-core bumped from 56.1.15 to 56.1.19; oat-sa/extension-tao-itemqti from 32.3.1 to 32.4.2; oat-sa/extension-tao-testqti from 50.1.5 to 50.2.1.1; oat-sa/extension-tao-itemqti-pci from 9.1.9 to 9.4.3.

CI Front-end Test Refactor

Layer / File(s) Summary
CI Matrix Node version
.github/workflows/continuous-integration.yaml
CI matrix include override changed to use Node.js 20 for the Ubuntu job.
Install Chromium dependencies
.github/workflows/continuous-integration.yaml
Apt package list for Chromium expanded (adds fonts-liberation) and package listing reshaped.
Puppeteer / Chromium Environment Setup
.github/workflows/continuous-integration.yaml
Adds step to write PUPPETEER_EXECUTABLE_PATH, PUPPETEER_SKIP_CHROMIUM_DOWNLOAD, CHROME_BIN, CHROMIUM_BIN and consolidated GRUNT_CHROME_FLAGS to $GITHUB_ENV.
FE QUnit runner script
.github/scripts/run-fe-qunit.sh
New bash helper that runs a named Grunt QUnit suite with configurable retry attempts, optional GRUNT_CHROME_FLAGS forwarding, and JUnit report output to ../../../junit-reports.
Per-suite Grunt Front-end Test Steps
.github/workflows/continuous-integration.yaml, .github/scripts/run-fe-qunit.sh
Replaces single aggregated Grunt test run with multiple steps; each invokes .github/scripts/run-fe-qunit.sh <suite>, runs npx grunt connect:test qunit_junit <suite> with --chrome-flags="$GRUNT_CHROME_FLAGS", and emits JUnit reports to ../../../junit-reports.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Release 2026 05 lts' directly corresponds to the primary objective of the pull request, which is updating the project to release version 2026.05 LTS as indicated by the version keyword update in composer.json and multiple dependency bumps.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release-2026-05-lts

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions

github-actions Bot commented May 8, 2026 •

Copy link
Copy Markdown
Contributor

Back-end summary PHP 8.3

🔗 Coverage report

💯 Total ✅ Passed ⏭️ Skipped ❌ Failed
4469 4444 25 0

@github-actions

github-actions Bot commented May 8, 2026

Copy link
Copy Markdown
Contributor

Front-end summary Node 16

💯 Total ✅ Passed ⏭️ Skipped ❌ Failed
2114 2114 0 0

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 2

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
.github/workflows/continuous-integration.yaml (1)

108-117: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Add an explicit guard when Chromium binary discovery returns empty.

If Line 113 finds no binary, Line 116 fails with an opaque error. Fail fast with a clear message before exporting and chmod.

Proposed fix
       - name: Find Puppeteer Chromium path
         if: ${{ matrix.node-version }}
         id: chromium-path
         working-directory: tao/views/build
         run: |
           CHROME_PATH=$(find ${{ github.workspace }}/tao/views/build/node_modules/puppeteer/.local-chromium -name "chrome" -type f 2>/dev/null | head -1)
+          if [ -z "$CHROME_PATH" ]; then
+            echo "::error::Chromium binary not found under puppeteer/.local-chromium"
+            exit 1
+          fi
           echo "path=$CHROME_PATH" >> $GITHUB_OUTPUT
           echo "Found Chromium at: $CHROME_PATH"
           chmod +x "$CHROME_PATH"
🤖 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 @.github/workflows/continuous-integration.yaml around lines 108 - 117, The
step with id "chromium-path" currently assumes CHROME_PATH from the find command
is non-empty and proceeds to export and chmod it; add an explicit guard after
setting CHROME_PATH to check if it's empty and if so fail fast with a clear
error (e.g., set a failing exit/status and echo a descriptive message),
otherwise continue to echo to $GITHUB_OUTPUT and run chmod; update references to
CHROME_PATH in this step (the variable assignment and the echo/chmod lines) so
the guard runs immediately after CHROME_PATH is computed.
🤖 Prompt for all review comments with 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.

Inline comments:
In @.github/workflows/continuous-integration.yaml:
- Around line 131-185: Each front-end test job step (e.g., the steps named
"Front-end tests (pcisamplestest)", "Front-end tests (qtiitempcitest)",
"Front-end tests (taotest)", etc.) currently stops the workflow on the first
failure; update every such step to include continue-on-error: true so later
suites and the final report/summary steps still run, and do not modify the final
failure gate step that aggregates results.
- Around line 22-23: The workflow pins node-version: '16', which is unsupported
on GitHub-hosted runners; update the node-version value in the CI workflow (the
node-version key in .github/workflows/continuous-integration.yaml) to a
supported LTS like '20' (or '22'/'24') and run the CI to confirm compatibility,
and if Puppeteer/qunit compatibility breaks, bump the
Puppeteer/grunt-contrib-qunit dependency to a version compatible with the chosen
Node LTS and re-run tests until green.

---

Outside diff comments:
In @.github/workflows/continuous-integration.yaml:
- Around line 108-117: The step with id "chromium-path" currently assumes
CHROME_PATH from the find command is non-empty and proceeds to export and chmod
it; add an explicit guard after setting CHROME_PATH to check if it's empty and
if so fail fast with a clear error (e.g., set a failing exit/status and echo a
descriptive message), otherwise continue to echo to $GITHUB_OUTPUT and run
chmod; update references to CHROME_PATH in this step (the variable assignment
and the echo/chmod lines) so the guard runs immediately after CHROME_PATH is
computed.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 694fe56f-999f-4438-8789-1020c75ec1e7

📥 Commits

Reviewing files that changed from the base of the PR and between 7caff5c and b7dd2f8.

📒 Files selected for processing (2)
  • .github/scripts/run-fe-qunit.sh
  • .github/workflows/continuous-integration.yaml
✅ Files skipped from review due to trivial changes (1)
  • .github/scripts/run-fe-qunit.sh

@github-actions

github-actions Bot commented May 8, 2026 •

Copy link
Copy Markdown
Contributor

Front-end summary Node 20

💯 Total ✅ Passed ⏭️ Skipped ❌ Failed
2114 2114 0 0

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with 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.

Inline comments:
In @.github/workflows/continuous-integration.yaml:
- Around line 131-199: The front-end test report publishing job is missing a
report_paths pattern so JUnit XMLs from the multiple suite runs (invoked by the
run-fe-qunit.sh steps like pcisamplestest, taotest, taoclientdiagnostictest,
etc.) are not collected; update the front-end report step (the job that
publishes front-end results) to include report_paths: 'junit-reports/**/*.xml'
(or an equivalent glob such as 'junit-reports/*/junit.xml') so all junit files
produced by the run-fe-qunit.sh invocations are aggregated.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 84c81f12-4e2a-4042-9fee-7688d8545035

📥 Commits

Reviewing files that changed from the base of the PR and between b7dd2f8 and 57cefc0.

📒 Files selected for processing (1)
  • .github/workflows/continuous-integration.yaml

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🧹 Nitpick comments (1)
.github/workflows/continuous-integration.yaml (1)

131-199: ⚡ Quick win

Prevent silent suite drops when using continue-on-error.

Because every front-end suite step is continue-on-error: true (for example, Line 133), a suite can fail before writing JUnit XML and still be omitted from the final count at Line 217. Add a guard that validates expected report files exist before publishing.

Proposed minimal guard step
+      - name: Verify front-end JUnit reports are complete
+        if: ${{ matrix.node-version }}
+        run: |
+          expected=14
+          actual=$(find junit-reports -type f -name '*.xml' 2>/dev/null | wc -l | tr -d ' ')
+          if [ "$actual" -lt "$expected" ]; then
+            echo "Expected at least $expected front-end JUnit reports, found $actual."
+            exit 1
+          fi
+
       - name: Publish a front-end test report
         if: ${{ matrix.node-version }}
         uses: mikepenz/action-junit-report@v3
🤖 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 @.github/workflows/continuous-integration.yaml around lines 131 - 199, The
workflow marks each Front-end tests step (the ones invoking
.github/scripts/run-fe-qunit.sh) with continue-on-error: true which lets a
failing suite skip producing JUnit XML and be omitted from the publisher; add a
guard step (either immediately after each run-fe-qunit.sh step or as a single
pre-publish check) that verifies the expected report file(s) exist (e.g. the
junit XML path pattern written by run-fe-qunit.sh) and fails if any are missing
so the publish step cannot silently ignore dropped suites; reference the test
steps that call run-fe-qunit.sh and the continue-on-error usage when adding the
check and ensure the guard runs before the JUnit publish/upload action.
🤖 Prompt for all review comments with 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.

Nitpick comments:
In @.github/workflows/continuous-integration.yaml:
- Around line 131-199: The workflow marks each Front-end tests step (the ones
invoking .github/scripts/run-fe-qunit.sh) with continue-on-error: true which
lets a failing suite skip producing JUnit XML and be omitted from the publisher;
add a guard step (either immediately after each run-fe-qunit.sh step or as a
single pre-publish check) that verifies the expected report file(s) exist (e.g.
the junit XML path pattern written by run-fe-qunit.sh) and fails if any are
missing so the publish step cannot silently ignore dropped suites; reference the
test steps that call run-fe-qunit.sh and the continue-on-error usage when adding
the check and ensure the guard runs before the JUnit publish/upload action.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c5c15ccd-58db-4273-a671-fcd1796183c1

📥 Commits

Reviewing files that changed from the base of the PR and between 57cefc0 and 3927c79.

📒 Files selected for processing (1)
  • .github/workflows/continuous-integration.yaml

@tikhanovichA
tikhanovichA merged commit 7a84326 into master May 8, 2026
4 of 5 checks passed
@tikhanovichA
tikhanovichA deleted the release-2026-05-lts branch May 8, 2026 12:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants