chore: migrate from Allure 2 to Allure 3#64
Conversation
- Replace allure-commandline@^2.37.0 with allure@^3.3.1 (TypeScript-based, no Java required) - Add allurerc.mjs config with awesome plugin and .jsonl history - Update e2e-tests.yml: new .jsonl history model, allure-framework/allure-report@v0 PR comment action - Update allure-pages.yml: artifact path allure-report/awesome/ for Allure 3 plugin output - Update .gitignore: add allure-history.jsonl
|
🚅 Deployed to the reqcore-pr-64 environment in applirank
|
📝 WalkthroughWalkthroughThis PR migrates Allure reporting from v2 to v3 by updating GitHub Actions workflows, introducing an allurerc.mjs configuration file, upgrading package dependencies, and adjusting artifact paths and history file formats to align with the new Allure v3 pipeline structure. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 Generate unit tests (beta)
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[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/e2e-tests.yml:
- Around line 121-127: Update the "Post Allure summary to PR" GitHub Action
step: change the uses reference from allure-framework/allure-report@v0 to a
maintained action (verify availability first) and set the report-directory input
to ./allure-report instead of ./; specifically update the step named "Post
Allure summary to PR" to point to a working action (e.g.,
simple-elf/allure-report-with-history or andgineer/allure-report) and ensure the
with: report-directory field is ./allure-report and github-token remains ${{
secrets.GITHUB_TOKEN }}.
ℹ️ Review info
Configuration used: defaults
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (5)
.github/workflows/allure-pages.yml.github/workflows/e2e-tests.yml.gitignoreallurerc.mjspackage.json
| - name: Post Allure summary to PR | ||
| if: ${{ !cancelled() && github.event_name == 'pull_request' }} | ||
| uses: allure-framework/allure-report@v0 | ||
| with: | ||
| report-directory: ./ | ||
| github-token: ${{ secrets.GITHUB_TOKEN }} | ||
| continue-on-error: true |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
allure-framework/allure-report GitHub action documentation v0
💡 Result:
The official documentation for the GitHub Action version allure-framework/allure-report@v0 is in the Allure Report docs under “GitHub Action integration”. It explains prerequisites (must generate an Allure 3 HTML report that contains {report-directory}/summary.json), required GitHub permissions, configuration, and quality-gate behavior. [1]
Minimal usage (from the docs):
permissions:
pull-requests: write
checks: write
- name: Run Allure Action
uses: allure-framework/allure-report@v0
with:
report-directory: "./allure-report"
github-token: ${{ secrets.GITHUB_TOKEN }}[1]
Notes from the same doc page:
- The action reads
summary.jsonfrom the generated HTML report directory to post a PR summary comment. [1] - If you use Allure quality gates, it also creates a GitHub Check and reads
{report-directory}/quality-gate.json. [1]
🏁 Script executed:
# Check if there are other references to this action in the codebase
rg "allure-report" --type yaml -B 2 -A 5Repository: reqcore-inc/reqcore
Length of output: 45
🏁 Script executed:
# Look for any documentation or comments about allure configuration in the repo
fd README -o CONTRIBUTING -o "*.md" | xargs rg -l "allure" 2>/dev/null | head -5Repository: reqcore-inc/reqcore
Length of output: 288
🌐 Web query:
allure-framework/allure-report releases tags v0 version history GitHub
💡 Result:
allure-framework/allure-report is not a GitHub repo anymore (404 Not Found), so there’s no “v0.*” tag/release history to retrieve from it. [1]
The Allure Report codebase/releases are published under:
- Allure 2:
allure-framework/allure2— use GitHub Tags / Releases pages. Its tags are 2.x (e.g.,2.36.0dated Dec 10, 2025) and do not include anyv0.*tags. [2][3] - Allure 3 (beta):
allure-framework/allure3— releases/tags are **v3.0.0-beta.*`. [4]
Sources
- [1] GitHub repository URL returns 404. ()
- [2]
allure-framework/allure2tags list (shows 2.x tags; e.g.,2.36.0on Dec 10, 2025). (github.com) - [3]
allure-framework/allure2releases page. (github.com) - [4]
allure-framework/allure3releases page (v3 beta tags). (github.com)
Citations:
- 1: https://github.com/allure-framework/allure2/tags
- 2: https://github.com/allure-framework/allure2/releases
- 3: https://github.com/allure-framework/allure3/releases?utm_source=openai
🏁 Script executed:
# Check the allurerc.mjs to see what report directory is configured
cat allurerc.mjsRepository: reqcore-inc/reqcore
Length of output: 559
🌐 Web query:
"allure-framework/allure-report" GitHub action marketplace
💡 Result:
I couldn’t find a GitHub Marketplace listing for the action repo allure-framework/allure-report. The official Allure docs still show it as a usable action by reference in workflows (e.g., uses: allure-framework/allure-report@v0). [1]
If you specifically need a Marketplace-listed Allure report action, common options include:
- simple-elf/allure-report-with-history (Marketplace: “Allure Report with history”). [2]
- andgineer/allure-report (Marketplace: “generate-allure-report”). [3]
Sources
[1] Allure Report docs – GitHub Action integration: (allurereport.org)
[2] GitHub Marketplace – “Allure Report with history”: (github.com)
[3] GitHub Marketplace – “generate-allure-report”: (github.com)
Citations:
- 1: https://allurereport.org/docs/integrations-github-action/?utm_source=openai
- 2: https://github.com/marketplace/actions/allure-report-with-history?utm_source=openai
- 3: https://github.com/marketplace/actions/generate-allure-report?utm_source=openai
🏁 Script executed:
# Check if this action exists by searching the GitHub Actions marketplace or common action repos
rg "allure-report" . --type yaml -B 5 -A 10Repository: reqcore-inc/reqcore
Length of output: 45
🏁 Script executed:
# Get the full context of the workflow around the allure action
sed -n '115,135p' .github/workflows/e2e-tests.ymlRepository: reqcore-inc/reqcore
Length of output: 752
🏁 Script executed:
# Try to access the allure-framework/allure-report repository directly
curl -s -o /dev/null -w "%{http_code}" https://api.github.com/repos/allure-framework/allure-reportRepository: reqcore-inc/reqcore
Length of output: 66
🏁 Script executed:
# Check if the action might be archived or under a different name
curl -s https://api.github.com/repos/allure-framework/allure-report 2>/dev/null | jq '.message, .archived' 2>/dev/null || echo "Repo not found"Repository: reqcore-inc/reqcore
Length of output: 79
Fix incorrect report-directory input and verify action availability.
The allure-framework/allure-report@v0 repository returns a 404—it appears to no longer exist or is archived. Additionally, the report-directory input is incorrect. Per the official Allure documentation, it should be ./allure-report (where the report is generated by allure generate), not ./. The action reads summary.json from the specified report directory, so using ./ will cause the action to fail.
Correction needed:
- name: Post Allure summary to PR
if: ${{ !cancelled() && github.event_name == 'pull_request' }}
uses: allure-framework/allure-report@v0
with:
report-directory: ./allure-report
github-token: ${{ secrets.GITHUB_TOKEN }}
continue-on-error: trueVerify that the action is still available and maintained; if not, consider using an alternative such as simple-elf/allure-report-with-history or andgineer/allure-report.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.github/workflows/e2e-tests.yml around lines 121 - 127, Update the "Post
Allure summary to PR" GitHub Action step: change the uses reference from
allure-framework/allure-report@v0 to a maintained action (verify availability
first) and set the report-directory input to ./allure-report instead of ./;
specifically update the step named "Post Allure summary to PR" to point to a
working action (e.g., simple-elf/allure-report-with-history or
andgineer/allure-report) and ensure the with: report-directory field is
./allure-report and github-token remains ${{ secrets.GITHUB_TOKEN }}.
1 participant
Summary
Type of change
Validation
DCO
Signed-off-by) viagit commit -sSummary by CodeRabbit
Tests
Chores