Skip to content

Conversation

@caponetto
Copy link

@caponetto caponetto commented Jul 29, 2025

Summary by CodeRabbit

  • New Features

    • Added detailed changelog entries for Elyra 4.0.0 release candidates, including dependency updates, security fixes, and new Python version support.
  • Dependency Updates

    • Upgraded Python package versions for requests, tornado, and jupyterlab-git.
  • Bug Fixes

    • Addressed security vulnerabilities and improved CI workflows.
  • Documentation

    • Updated installation, release, and changelog documentation to remove references to the Elyra code viewer extension.
  • Chores

    • Removed the Elyra code viewer extension from the codebase, build, and publishing process.

lresende and others added 9 commits July 29, 2025 09:24
Bumps [braces](https://github.com/micromatch/braces) from 3.0.2 to 3.0.3.
- [Changelog](https://github.com/micromatch/braces/blob/master/CHANGELOG.md)
- [Commits](micromatch/braces@3.0.2...3.0.3)

---
updated-dependencies:
- dependency-name: braces
  dependency-version: 3.0.3
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [tornado](https://github.com/tornadoweb/tornado) from 6.4.2 to 6.5.1.
- [Changelog](https://github.com/tornadoweb/tornado/blob/master/docs/releases.rst)
- [Commits](tornadoweb/tornado@v6.4.2...v6.5.1)

---
updated-dependencies:
- dependency-name: tornado
  dependency-version: 6.5.1
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [requests](https://github.com/psf/requests) from 2.32.3 to 2.32.4.
- [Release notes](https://github.com/psf/requests/releases)
- [Changelog](https://github.com/psf/requests/blob/main/HISTORY.md)
- [Commits](psf/requests@v2.32.3...v2.32.4)

---
updated-dependencies:
- dependency-name: requests
  dependency-version: 2.32.4
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
---
updated-dependencies:
- dependency-name: form-data
  dependency-version: 4.0.4
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@coderabbitai
Copy link

coderabbitai bot commented Jul 29, 2025

Walkthrough

This change set removes the Elyra Code Viewer extension from the project. All related files, configuration entries, documentation references, and build/publish steps for the code viewer extension are deleted or updated. Dependency versions for several Python packages are also bumped, and new release notes are added to the changelog.

Changes

Cohort / File(s) Change Summary
Documentation - Remove Code Viewer Extension References
README.md, docs/source/getting_started/installation.md, docs/source/developer_guide/release.md
Removed all references to the Elyra Code Viewer extension from installation and release documentation.
Release Notes Update
docs/source/getting_started/changelog.md
Added new entries for Elyra 4.0.0 release candidates 1-5, detailing dependency updates, security fixes, CI/tooling improvements, and other changes.
Build and Release Process Cleanup
create-release.py, pyproject.toml
Removed all build, packaging, and publishing steps for the Elyra Code Viewer extension; updated dependency for jupyterlab-git; removed commented-out labextension entry.
Python Dependency Updates
etc/generic/requirements-elyra.txt
Bumped requests to 2.32.4 and tornado to 6.5.1.
Pipeline Editor - Command Update
packages/pipeline-editor/src/PipelineEditorWidget.tsx
Changed the code viewer command ID from 'elyra-code-viewer:open' to 'code-viewer:open'.
Remove Elyra Code Viewer Extension Implementation
labextensions/elyra_code_viewer_extension/__init__.py, packages/code-viewer/*
Deleted all source, configuration, and build files for the Elyra Code Viewer extension, including TypeScript, Python, JSON, and CSS files.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~18 minutes

Poem

A hop, a skip, a leap—away
The code viewer’s gone today!
Docs and configs swept up neat,
Pip and npm in retreat.
Dependencies fresh, changelogs new,
Elyra’s garden’s trimmed and true.
🐇✨ Onward to the next review!

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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.

❤️ Share
🪧 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.

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: 1

🧹 Nitpick comments (2)
docs/source/developer_guide/release.md (1)

212-212: Typo: “awerness” → “awareness”

Minor spelling nit in the newly edited sentence.

- To raise awerness for new releases
+ To raise awareness for new releases
docs/source/getting_started/changelog.md (1)

27-31: Remove the duplicated bullet for the code-viewer switch

- Switch from elyra-code-viewer to jupyterlab-code-viewer - [#3265] appears twice in the same 4.0.0 rc2 section. Keeping both clutters the changelog and needlessly inflates the diff.

@@
 - Update JupyterLab version compatibility all way to 4.3.x  - [#3293](https://github.com/elyra-ai/elyra/pull/3293)
 - Switch from elyra-code-viewer to jupyterlab-code-viewer - [#3265](https://github.com/elyra-ai/elyra/pull/3265)
 
 See the full changelog below:
 
- - Switch from elyra-code-viewer to jupyterlab-code-viewer - [#3265](https://github.com/elyra-ai/elyra/pull/3265)
+<!-- duplicate removed -->
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4eb9319 and 037e811.

⛔ Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (16)
  • README.md (0 hunks)
  • create-release.py (1 hunks)
  • docs/source/developer_guide/release.md (1 hunks)
  • docs/source/getting_started/changelog.md (1 hunks)
  • docs/source/getting_started/installation.md (0 hunks)
  • etc/generic/requirements-elyra.txt (1 hunks)
  • labextensions/elyra_code_viewer_extension/__init__.py (0 hunks)
  • packages/code-viewer/install.json (0 hunks)
  • packages/code-viewer/package.json (0 hunks)
  • packages/code-viewer/setup.py (0 hunks)
  • packages/code-viewer/src/CodeViewerWidget.ts (0 hunks)
  • packages/code-viewer/src/index.ts (0 hunks)
  • packages/code-viewer/style/index.css (0 hunks)
  • packages/code-viewer/tsconfig.json (0 hunks)
  • packages/pipeline-editor/src/PipelineEditorWidget.tsx (1 hunks)
  • pyproject.toml (1 hunks)
💤 Files with no reviewable changes (10)
  • packages/code-viewer/package.json
  • packages/code-viewer/style/index.css
  • README.md
  • packages/code-viewer/install.json
  • packages/code-viewer/src/index.ts
  • packages/code-viewer/setup.py
  • docs/source/getting_started/installation.md
  • packages/code-viewer/tsconfig.json
  • labextensions/elyra_code_viewer_extension/init.py
  • packages/code-viewer/src/CodeViewerWidget.ts
🔇 Additional comments (3)
etc/generic/requirements-elyra.txt (1)

16-17: Verify downstream compatibility of new requests 2.32.4 / tornado 6.5.1 pins

Both bumps are patch/feature releases that should be safe, but:

  • tornado 6.5.x just introduced breaking TLS changes that bit some JupyterLab 4.2+ installs.
  • requests 2.32.4 only fixes a metadata issue but pulls in urllib3 2.x if un-pinned elsewhere.

Please run the integration test matrix (JupyterLab, notebook execution, pipeline submission) before cutting a release to ensure nothing regresses.

packages/pipeline-editor/src/PipelineEditorWidget.tsx (1)

122-123: All code references updated for renamed command
A global search (rg -n "'elyra-code-viewer:open'") found no occurrences of the old command name in the repo.

Please manually verify the following remain up-to-date:

  • Any user keybindings in the Advanced Settings Editor
  • External extension or fixture configurations (e.g., pipeline-services, test fixtures)
create-release.py (1)

607-607: LGTM! Correctly removes code-viewer-extension dependency.

The removal of "code-viewer-extension" from the elyra-pipeline-editor-extension packages list aligns with the PR objective to remove the internal Elyra Code Viewer extension and switch to jupyterlab-code-viewer. This change ensures the pipeline editor extension will no longer include the deprecated code viewer component in future releases.

"jupyterlab~=4.4", # comment out to use local jupyterlab
"jupyterlab-lsp~=5.1.0", # comment out to use local jupyterlab
"jupyterlab-git~=0.50.0", # Avoid breaking 1.x changes
"jupyterlab-git~=0.51.2", # Avoid breaking 1.x changes
Copy link

Choose a reason for hiding this comment

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

💡 Verification agent

🧩 Analysis chain

Double-check jupyterlab-git 0.51.2 with JupyterLab 4.4

0.51.2 advertises JL 4.0–4.2 support; JL 4.4 APIs changed slightly (notably the diff widget). If you hit MIME-render or model-DB errors, you may need to wait for ≥0.52 or pin JL to 4.2 in this distribution.


🌐 Web query:

What JupyterLab versions does jupyterlab-git 0.51.2 support? Please check the PyPI metadata or GitHub release notes for jupyterlab-git 0.51.2.

💡 Result:

The jupyterlab-git extension version 0.51.2 is compatible with JupyterLab versions 4.0 and later. For earlier versions of JupyterLab (2.x and 3.x), the extension provides separate branches:

  • JupyterLab 3.x: Use the 3.x branch.
  • JupyterLab 2.x: Use the 2.x branch.

These branches ensure compatibility with the respective JupyterLab versions. (github.com)

Citations:


Update jupyterlab-git compatibility note

The jupyterlab-git 0.51.2 release officially targets JupyterLab 4.0 and later (including 4.4), so the warning about only 4.0–4.2 support is out of date. Retain a brief note on upgrading if you hit API breakage:

• File: pyproject.toml (line 32)
• Replace the existing comment on that dependency with something like:

- "jupyterlab-git~=0.51.2",  # Avoid breaking 1.x changes
+ "jupyterlab-git~=0.51.2",  # Compatible with JupyterLab 4.0+ (incl. 4.4); if you see diff-widget or model/DB errors, upgrade to ≥0.52 or pin JL to 4.2
🤖 Prompt for AI Agents
In pyproject.toml at line 32, update the comment on the "jupyterlab-git~=0.51.2"
dependency to reflect that this version supports JupyterLab 4.0 and later,
including 4.4. Replace the outdated note about only supporting 4.0–4.2 with a
brief mention advising users to upgrade if they encounter API breakage.

@codecov-commenter
Copy link

codecov-commenter commented Jul 29, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.50%. Comparing base (1613654) to head (037e811).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #125      +/-   ##
==========================================
- Coverage   80.51%   80.50%   -0.02%     
==========================================
  Files         151      151              
  Lines       19486    19484       -2     
  Branches      483      487       +4     
==========================================
- Hits        15690    15685       -5     
- Misses       3611     3617       +6     
+ Partials      185      182       -3     

☔ 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.

@caponetto caponetto requested a review from jesuino August 1, 2025 10:26
Copy link

@jesuino jesuino left a comment

Choose a reason for hiding this comment

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

It looks good to me!
It seems to be mostly versions updates and the removal of the custom code viewer in favor of the one provided by JupyterLab.

@caponetto caponetto merged commit b15353d into opendatahub-io:main Aug 4, 2025
22 checks passed
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