Issue to trigger new releases

[ablaom]

@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/15884

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.9.12 -m "<description of version>" edb732a13cc68a75968e8c6a90457e1041c01710
git push origin v0.9.12

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/16126

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.9.13 -m "<description of version>" 4b2fb5f2bd0e29fcd632f1d7d4bf343dfe7ff4b9
git push origin v0.9.13

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/16126

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.9.13 -m "<description of version>" 5d74ff69196de32890f678eae5989c27e325256e
git push origin v0.9.13

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/16385

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.10.0 -m "<description of version>" 29cce89c836514bc040aa1e09c07a8044659edf2
git push origin v0.10.0

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/16728

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.10.1 -m "<description of version>" 3f4f7edec90cf594d6943084688730a2c5edaf64
git push origin v0.10.1

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/17164

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.11.0 -m "<description of version>" edd140b590fe87c0b981572dfb76dbbfa00e8be6
git push origin v0.11.0

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/18172

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.11.1 -m "<description of version>" da24bd4066bb3929faf53629122901038ab866b9
git push origin v0.11.1

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/18219

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.11.2 -m "<description of version>" e70985cddaf77f4fca26a99f3c47e71a281bc0bc
git push origin v0.11.2

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Error while trying to register: Changing package repo URL not allowed, please submit a pull request with the URL change to the target registry and retry.

[ablaom]

@JuliaRegistrator register

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/98589

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.16.13 -m "<description of version>" d1701d8d8a78e37594e24266b0453a30d1183ada
git push origin v0.16.13

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/98941

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.16.14 -m "<description of version>" 613aa845c3373e151e52e103fba5ad8cfcb027cd
git push origin v0.16.14

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/99656

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.16.15 -m "<description of version>" c2cc862891907d777bd0d75fe340c32c7aebb43c
git push origin v0.16.15

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/102484

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.16.16 -m "<description of version>" 857d0b79a946dd0f2e167a822a66d5d23cd71290
git push origin v0.16.16

[ablaom]

@JuliaRegistrator register branch=master

Release notes:

• (new model) Add partitioned least squares model, PartLS, from PartitionedLS.jl, to the model registry (Add PartionedLS model to registry #553)

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/104858

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.16.17 -m "<description of version>" c1d1c4c967bc3bd53e33175d8dcf1a8e57542282
git push origin v0.16.17

[ablaom]

@JuliaRegistrator register branch=master

Release notes:

• (mildly breaking) The FeatureSelector appearing in the Model Registry (as inspected using models()) is now provided by the FeatureSelection.jl package (pkg = FeatureSelection) instead of the MLJModels.jl package. This reflects a code migration, not a change in behaviour of the model. The only foreseeable breakage is any code with a call like @load FeatureSelection pkg=MLJModels; which was always redundant anyway, because the model never required explicit loading in MLJ.

• (new models) Add the RecursiveFeatureElimination model wrapper to the model registry (this will be a built-in model in next MLJ release).

• (new feature) Model wrappers, such TunedModel, BalancedModel and IteratedModel, can now be listed using models(...; wrappers=true).

• (internals) The name of a model in the Model Registry now reflects the name a model constructor instead of a model type (which are the same for all current models that aren't composite models aka, model wrappers). Model wrappers (or other models with contractor names different from the type) must overload a new trait MLJModelInterface.constructor to define the constructor for each type. For example, we now have constructor(::DeterministicTunedModel) = TunedModel. For more on this, see Base the Model Registry on constructors, rather than model types; and ancillary changes #558.

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/108288

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.17.0 -m "<description of version>" 5340efe2ae90f0eaf9f076a29f4601ff3944d8ae
git push origin v0.17.0

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/108339

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.17.1 -m "<description of version>" 6f573c2735fc16c70979b8c2bba9d807f522e131
git push origin v0.17.1

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/109316

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.17.2 -m "<description of version>" ea3d163d85b0cdcebe577c6bd7593512d17b7dc0
git push origin v0.17.2

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/110811

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.17.3 -m "<description of version>" f0b73f13123a5a6680433267f9660486d1f4aeb5
git push origin v0.17.3

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/112261

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.17.4 -m "<description of version>" 9d4c476afd2734ddabe1ca5f402c50a1c0626f55
git push origin v0.17.4