Issue for triggering new releases

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/17044

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

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/18169

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.4.1 -m "<description of version>" 6fed9cb5b1f92a03ed83303997abbf16c5854d4d
git push origin v0.4.1

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/19475

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.4.2 -m "<description of version>" 250c0550168fdf33957e776ebb0b44de04b6fa3c
git push origin v0.4.2

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/20426

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.4.3 -m "<description of version>" 3b1b35db56da5c764dd5248259d14bc8bd3db790
git push origin v0.4.3

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/21399

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.5.0 -m "<description of version>" 3e989d5e7d677d73b4c06d087f9a10c6fadcd511
git push origin v0.5.0

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

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

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/21672

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.5.1 -m "<description of version>" 8c3e948d6db3c39b47f201fdd5601c7b63a7a08f
git push origin v0.5.1

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/22912

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.5.2 -m "<description of version>" 7314ca514c625bfbabff117655667ee74f502eba
git push origin v0.5.2

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/23306

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.5.3 -m "<description of version>" 3785f0d88fa09e860bda579613c886abcbe90c01
git push origin v0.5.3

Also, note the warning: Version 0.5.3 skips over 0.5.2
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/22912

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.5.2 -m "<description of version>" 3f67fbca8c2b5ebe473d142374c946a68a4cbe1f
git push origin v0.5.2

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/92206

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

[ablaom]

@JuliaRegistrator register branch=master

Release notes:

• (breaking) Bump MLJBase compatibility to version 1. When using without MLJ, users may need to explicitly import StatisticalMeasures.jl. See also the MLJBase 1.0 migration guide (Update code and tests to address migration of measures MLJBase -> StatisticalMeasures #194)

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/92206

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

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/99405

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.8.1 -m "<description of version>" 60ad34450e6419e5a8491de03c4a0008e8a7144d
git push origin v0.8.1

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/102482

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.8.2 -m "<description of version>" 39d6cb46787d998aee5b7de315f8941142d231aa
git push origin v0.8.2

[ablaom]

@JuliaRegistrator register branch=master

Release notes:

• Include full evaluation objects (key = :evaluation) in history entries (Add entire evaluation objects to history #210)

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/103060

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.8.3 -m "<description of version>" 4f1dd7176078572979bba3b4e5c1ddb7af693a24
git push origin v0.8.3

[ablaom]

@JuliaRegistrator register branch=master

Release notes:

• (enhancement) Implement feature importances that expose the feature importances of the optimal atomic model (add feature importances support for tuned models #213)

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/103528

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.8.4 -m "<description of version>" 9fe1f52477c09e00c046e77e1533c11def060e49
git push origin v0.8.4

[ablaom]

@JuliaRegistrator register branch=master

Release notes:

• Write the PerformanceEvaluation objects computed for each model (hyper-parameter set) to the history, or write compact versions of the same (CompactPeformanceEvaluation objects) by providing TunedModel(...) a new option compact_history=true. The evaluation objects are accessed like this: evaluation = report(mach).history[index].evaluation, where mach is a machine associated with the TunedModel instance. For more on the differences between PerformanceEvaluation and CompactPerformanceEvaluation objects, refer to their document strings. (In MLJTuning 0.5.3 and 0.5.4 an experimental feature already introduced PerformanceEvalution objects to the history, but with no option to write the compact form. In the current release, compact objects are written by default.)

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/106297

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

[ablaom]

@JuliaRegistrator register branch=master

Release notes:

• (new feature) Add logger option to TunedModel wrapper, for logging internal model evaluations to an ML tracking platform, such as MLflow via MLJFlow.jl. Default should be nothing for no logging (Adding loggers into TunedModels #193). The logger must support asynchronous messaging if TunedModel(model, ...) is specified with the option acceleration=CPUThreads() or CPUProcesses(). Currently, CPU1() (the default) is supported by MLJFlow.jl's loggers, while ansynchronous support is a work in progress; see Implementing channel control for experiment creation MLJFlow.jl#41 Adding loggers into TunedModels #193.

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/107292

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.8.6 -m "<description of version>" 1af0202b7fc256e03c15a9604696e6092a0b141e
git push origin v0.8.6

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/107292

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.8.6 -m "<description of version>" 1af0202b7fc256e03c15a9604696e6092a0b141e
git push origin v0.8.6

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/107292

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.8.6 -m "<description of version>" 1af0202b7fc256e03c15a9604696e6092a0b141e
git push origin v0.8.6

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/108129

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.8.7 -m "<description of version>" 66581bcb92869a456684b41c01637a0be8a14593
git push origin v0.8.7

[ablaom]

@JuliaRegistrator register branch=master

Release notes:

• Change default logger from nothing to MLJBase.default_logger() (which can be reset with MLJBase.default_logger(new_logger)) Make the global default_logger() the default logger in TunedModel(logger=...) #221

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/111329

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.8.8 -m "<description of version>" 1421263d8404306621152e3b8303828ffce704f1
git push origin v0.8.8