Skip to content

Conversation

@bentsherman
Copy link
Member

The 25.10 migration notes currently say that the legacy plugin index can still be used, but AFAIK this support was completely removed in 25.10

@pditommaso can the NXF_PLUGINS_TEST_REPOSITORY env var still be used? If not then we should add a deprecation note

@bentsherman bentsherman requested a review from pditommaso January 5, 2026 19:42
@bentsherman bentsherman requested a review from a team as a code owner January 5, 2026 19:42
@netlify
Copy link

netlify bot commented Jan 5, 2026

Deploy Preview for nextflow-docs-staging ready!

Name Link
🔨 Latest commit f38e6a5
🔍 Latest deploy log https://app.netlify.com/projects/nextflow-docs-staging/deploys/695c1413efa66c00083d5fe9
😎 Deploy Preview https://deploy-preview-6702--nextflow-docs-staging.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@bentsherman bentsherman changed the title docs: Update migration node for plugin registry docs: Update migration note for plugin registry Jan 5, 2026
Copy link
Collaborator

@christopher-hakkaart christopher-hakkaart left a comment

Choose a reason for hiding this comment

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

Approved from an editorial perspective. One minor suggestion to align with the direction we are taking for reference/definition lists.

Will need someone else to confirm the content is accurate as of 25.10

: :::{versionadded} 20.10.0
:::
: Defines the path location of the SCM config file .
: Defines the path location of the SCM config file.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
: Defines the path location of the SCM config file.
: The path location of the SCM config file.

Copy link
Member

@pditommaso pditommaso left a comment

Choose a reason for hiding this comment

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

can the NXF_PLUGINS_TEST_REPOSITORY env var still be used? If not then we should add a deprecation note

it should be still in place

final repos = SysEnv.get('NXF_PLUGINS_TEST_REPOSITORY')

Comment on lines -197 to -202
The legacy plugin index can still be used by setting the `NXF_PLUGINS_REGISTRY_URL` environment variable:

```bash
export NXF_PLUGINS_REGISTRY_URL="https://raw.githubusercontent.com/nextflow-io/plugins/main/plugins.json"
```

Copy link
Member

Choose a reason for hiding this comment

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

Why is this removed?

final url = env.get('NXF_PLUGINS_REGISTRY_URL')
if( !url ) {
log.trace "Using default plugins url: ${NEXTFLOW_PLUGINS_REPO}"
return NEXTFLOW_PLUGINS_REPO
}

Copy link
Member Author

Choose a reason for hiding this comment

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

I thought you said that 25.10 doesn't support the legacy index? Isn't that why we don't publish plugins requiring >=25.10 to the legacy index?

Copy link
Member

Choose a reason for hiding this comment

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

I got your point, however technically both NXF_PLUGINS_TEST_REPOSITORY and NXF_PLUGINS_REGISTRY_URL are still there

Copy link
Member Author

Choose a reason for hiding this comment

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

Then I am confused. Does 25.10 still support the legacy index or not?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants