Issue to trigger releases

[ablaom]

No description provided.

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Error while trying to register: Action not recognized: registe

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/16172

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.13.9 -m "<description of version>" a1966a2756823cc0995ec1763374e0c9540f4688
git push origin v0.13.9

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Error while trying to register: "Tag with name v0.13.10 already exists and points to a different commit"

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/17002

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.14.0 -m "<description of version>" b62fa7b9d15ef6102b29a179e360d49d621d4171
git push origin v0.14.0

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/17157

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.14.1 -m "<description of version>" d93ef2f1095d9037af116b5d9d861e8ae7e6821b
git push origin v0.14.1

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/17667

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.14.2 -m "<description of version>" 730f3df4c4bb547e8f05a813efe28a36773ad71b
git push origin v0.14.2

[ablaom]

@JuliaRegistrator register

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/17949

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.14.4 -m "<description of version>" 0dc0f1d954c920aba0240d0b9e516ecbea13dd69
git push origin v0.14.4

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/18317

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.14.5 -m "<description of version>" 359635d46574dfd7d1b09af9f4cfd2b0780eaac8
git push origin v0.14.5

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/18483

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.14.6 -m "<description of version>" 11f1ab1701ed3a6abcc00c742d8a448fe2a30845
git push origin v0.14.6

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/19474

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.14.7 -m "<description of version>" 2c22918f6b6e11f87093bede6460bde513b4646d
git push origin v0.14.7

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Error while trying to register: Version 1.1.0 already exists

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/99363

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 v1.1.1 -m "<description of version>" 3ef17256fdb27441232807ba566d7e13016851d9
git push origin v1.1.1

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/102039

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 v1.1.2 -m "<description of version>" 30687fb48250a794d187a46a03d4daa6f2a30fd3
git push origin v1.1.2

[ablaom]

@JuliaRegistrator register branch=master

Release notes:

• (enhancement) Expose feature_importances in pipelines with a supporting supervised component, and in TransformedTargetModels with supporting atomic model (Allow Pipeline and TransformedTargetModel to support feature importances #963)

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/103051

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 v1.2.0 -m "<description of version>" 0725e908321a4fe5852a0b2716e9fd8c194447d3
git push origin v1.2.0

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/103058

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 v1.2.1 -m "<description of version>" 5046989170f4a948a1371cb4b0d4773d5e1ed628
git push origin v1.2.1

[ablaom]

@JuliaRegistrator register branch=master

Release notes:

• (Performance enhancement) Remove type instability for predict(mach::Machine, ...) in the easy and typical case that mach does not wrap a Symbol model (Address some predict/transform type instabilities #969)

• (New feature) Give evaluate and evaluate! the option compact=true, to return a CompactPerformanceEvaluation object with minimal memory footprint (Add CompactPerformanceEvaluation objects and the option in evaluate! to construct them #973)

• (New feature) Add an InSample() resampling strategy that trains and tests on the same data (whatever is specified by rows, or all supplied data) (Add InSample resampling strategy #975)

• (Display improvement) Split the table displayed as part of an PerformanceEvaluation object over two tables, if needed, to deal with overly wide tables (Add CompactPerformanceEvaluation objects and the option in evaluate! to construct them #973)

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/106224

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 v1.3.0 -m "<description of version>" d5f33985c5ddf5222eecf923777d8cace2aa6103
git push origin v1.3.0

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/108125

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 v1.4.0 -m "<description of version>" ffe0ac27affb643df15f26b5dce2f38210c1551d
git push origin v1.4.0

[ablaom]

@JuliaRegistrator register branch=master

Release notes:

• (enhancement) Add facility to specify a logger globally, with a setter default_logger(logger), and a getter default_logger() (Add a default_logger #979)

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/109709

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 v1.5.0 -m "<description of version>" 5739a73879bd0c2ff034dd8a490d79ffe7ffc4d5
git push origin v1.5.0

[ablaom]

@JuliaRegistrator register branch=master

Release notes:

• (enhancment) Arrange that pipelines support transformers that need a target variable for training (Add support in pipelines for Unsupervised models for which target_in_fit is true #984)

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/110289

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 v1.6.0 -m "<description of version>" 0849be77fb4e76ba222052abc9c7e5349eebaac0
git push origin v1.6.0

[ablaom]

@JuliaRegistrator register branch=master

Release notes:

• Relax some restrictions on model types in evaluate/evaluate! (Relax restrictions on model type in resampling (evaluate!) #985)

[JuliaRegistrator]

Error while trying to register: Version 1.6.0 already exists

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/111328

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 v1.7.0 -m "<description of version>" 4e8c0871aadf42807239ab6b32a38965dcaa0788
git push origin v1.7.0