Skip to content

Commit d011970

Browse files
committed
Unlist timeline subheadings
Signed-off-by: Ben Sherman <bentshermann@gmail.com>
1 parent de7aaa1 commit d011970

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/migrating-plugin-registry.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -28,21 +28,21 @@ The [legacy plugin index](https://github.com/nextflow-io/plugins) will be deprec
2828
The following timeline is tentative and subject to modification.
2929
:::
3030

31-
### Nextflow 25.04
31+
<h3>Nextflow 25.04</h3>
3232

3333
The Nextflow plugin registry is available as a private beta. Nextflow 25.04 can use the Nextflow plugin registry as an opt-in feature. The Nextflow plugin registry will be automatically kept up-to-date with the [legacy plugin index](https://github.com/nextflow-io/plugins).
3434

3535
During this time, plugin developers are encouraged to experiment with the Gradle plugin and plugin registry.
3636

37-
### Nextflow 25.10
37+
<h3>Nextflow 25.10</h3>
3838

3939
The Nextflow plugin registry will be generally available. Nextflow 25.10 will use the plugin registry by default. The legacy plugin index will be **closed to new pull requests**.
4040

4141
Developers will be required to publish to the Nextflow plugin registry. To ensure continued support for older versions of Nextflow, the legacy plugin index will be automatically kept up-to-date with the Nextflow plugin registry.
4242

43-
### Nextflow 26.04
43+
<h3>Nextflow 26.04</h3>
4444

45-
Nextflow 25.10 will only be able to use the Nextflow plugin registry.
45+
Nextflow 26.04 will only be able to use the Nextflow plugin registry.
4646

4747
At some point in the future, the legacy plugin index will be **frozen** -- it will no longer receives updates from the Nextflow plugin registry. To ensure continued support for older versions of Nextflow, the legacy plugin index will remain available indefinitely.
4848

0 commit comments

Comments
 (0)