Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-68816

Only versioned packages for streams that do not have full life-stream option

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • rhel-10.0
    • None
    • nodejs
    • None
    • Versioned names for default streams getting EOL
    • 0% To Do, 0% In Progress, 100% Done
    • rhel-pt-ruby-nodejs
    • False
    • Hide

      None

      Show
      None
    • PT PRNDL 2025 S02

      Following PM's guidance: https://docs.google.com/document/d/1bO4Pr488yrOaJIvf5ZIuQbuhrfi8q8v7UHg_QQ96X38/view

      On RHEL-9, streams like Node.js 16 or similar, that are the default option and have a limited lifecycle, cause issues – customers install it using dnf install nodejs and get a package that has no support any more. Changing the default is not possible, because it would break customer's applications, but keeping the default being EOL causes troubles to some customers.

      In RHEL-10, we would like to avoid this confusion and only have nodejs22 available. That means, dnf install nodejs will fail. A user would need to run dnf install nodejs22 specifically, which should make it more explicit that they install something EOL.

              jstanek@redhat.com Jan Stanek
              hhorak@redhat.com Honza Horak
              Jan Stanek Jan Stanek
              rhel-nodejs-qe bot rhel-nodejs-qe bot
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: