feat: remove the legacy library viewing and editing page

[salman2013]

Description

Removes the legacy library (V1) tab, routes, and associated UI from Studio Home. The migration wizard (/libraries-v1/migrate) is preserved to allow users to migrate existing legacy library content to V2.

Testing instructions

** Legacy Library Tab should not show on the studio home page**
** Library Tab (Library v2) should work properly:**

1. Log in to Studio and navigate to the Studio Home (/home).
2. Confirm the Libraries tab is visible and clicking it navigates to /libraries.
3. Click New Library — confirm it opens the V2 library creation page.
4. Create or open an existing V2 library and confirm normal editing works.

Legacy routes are removed:

1. Navigate directly to /libraries-v1 — confirm it returns a 404 / "not found" page.
2. Navigate directly to /libraries-v1/create — confirm it also returns a 404 / "not found" page.
3. Confirm there is no legacy Libraries tab on Studio Home.

Best Practices Checklist

We're trying to move away from some deprecated patterns in this codebase. Please
check if your PR meets these recommendations before asking for a review:

• Any new files are using TypeScript (.ts, .tsx). (N/A — no new files added)
• Avoid propTypes and defaultProps in any new or modified code. (N/A — no new props introduced)
• Tests should use the helpers in src/testUtils.tsx (specifically initializeMocks) (N/A — existing tests updated, no new test files)
• Do not add new fields to the Redux state/store. Use React Context to share state among multiple components. (N/A — Redux state only reduced, nothing added)
• Use React Query to load data from REST APIs. See any apiHooks.ts in this repo for examples. (N/A — no new API calls)
• All new i18n messages in messages.ts files have a description for translators to use. (N/A — no new i18n messages)
• Avoid using ../ in import paths. To import from parent folders, use @src, e.g. import { initializeMocks } from '@src/testUtils'; instead of from '../../../../testUtils' (N/A — no new imports added)

Settings

EDX_PLATFORM_REPOSITORY: https://github.com/openedx/openedx-platform.git
EDX_PLATFORM_VERSION: master

[openedx-webhooks]

Thanks for the pull request, @salman2013!

This repository is currently maintained by @bradenmacdonald.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.57%. Comparing base (3b6ae01) to head (620cb12).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #3080      +/-   ##
==========================================
- Coverage   95.64%   95.57%   -0.07%     
==========================================
  Files        1403     1403              
  Lines       33307    33294      -13     
  Branches     7570     7561       -9     
==========================================
- Hits        31855    31822      -33     
- Misses       1402     1421      +19     
- Partials       50       51       +1     

☔ View full report in Codecov by Harness.
📢 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.

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

This PR removes the legacy (v1) libraries experience from Studio Home, leaving only the v2 libraries tab and v2 library creation flow, and updates navigation/tests accordingly.

Changes:

• Removed the legacy libraries tab, route handling, and related props/state.
• Updated migration exit navigation to return to the v2 libraries area.
• Simplified/updated tests to reflect the removal of v1 libraries UI and routes.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
src/studio-home/tabs-section/index.tsx	Removes legacy libraries tab/state and simplifies tab routing to v2 libraries only.
src/studio-home/tabs-section/TabsSection.test.tsx	Deletes legacy libraries tests and updates navigation expectations to /libraries.
src/studio-home/hooks.tsx	Stops exposing librariesV1Enabled from the studio home hook.
src/studio-home/StudioHome.tsx	Removes v1 library button logic and always navigates to v2 create page.
src/studio-home/StudioHome.test.tsx	Removes tests covering v1-only/v2-only button behavior and legacy create navigation.
src/legacy-libraries-migration/LegacyLibMigrationPage.tsx	Changes “Exit” navigation target from /libraries-v1 to /libraries.
src/legacy-libraries-migration/LegacyLibMigrationPage.test.tsx	Updates expectation for exit navigation to /libraries.
src/index.jsx	Removes /libraries-v1 and /libraries-v1/create routes and legacy create import.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[irfanuddinahmad]

Two template housekeeping items:

Testing instructions are empty — the "## Testing instructions" section has no content. Given the scope of what changed (tab removed, routes removed, exit navigation updated), reviewers need guidance on how to verify the happy path (V2 tab still works, migration flow still exits correctly) and the removed paths (legacy tab is gone, old routes 404 or redirect).

Best Practices Checklist is unchecked — all boxes are [ ]. Even if everything is N/A for a deletion PR, it is worth a quick pass so reviewers know the checklist was considered.

[salman2013]

@kdmccormick, @feanil Just a question should we also remove the migrate legacy library page in this scope? This page appears from the legacy library tab, which has been removed in this PR, so there is no way to access it other than manually typing the URL.

---

Migrate legacy library

---

---

The Migrate legacy library page access from the legacy library tab, which has been removed in this PR.

---

[feanil]

I think it makes sense to remove the migrate legacy library page if it was only reachable from here.

[kdmccormick]

@salman2013 @feanil @irfanuddinahmad In Verawood, we're getting rid of the ability to create and edit legacy library content. But, the existing usages of legacy library content needs to keep working until Xylon, and the Legacy->V2 migration workflow also needs to keep working until Xylon.

Check out the "Removal" section here: openedx/openedx-platform#37931

[salman2013]

@kdmccormick Thanks for the heads-up. Just to confirm my understanding of this comment.

In Verawood, we're getting rid of the ability to create and edit legacy library content."But, the existing usages of legacy library content needs to keep working until Xylon"

you mean the legacy library tab should not be remove just the edit and create option should be remove right?

[salman2013]

@bradenmacdonald Could you also review this PR? It is a follow-up to #3077

[kdmccormick]

We will need to partially revert this PR-- see #2911 (comment) for more details.

[bradenmacdonald]

I agree that we need to have a v1 library listing page if we want to add an "Export" button for each v1 library, but I don't think it should be a straight revert - I replied on that other thread.