Issue to trigger releases

[pebeto]

No description provided.

[pebeto]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/90194

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

[ablaom]

@JuliaRegistrator register branch=master

Release notes:

• Address breaking changes caused by migration of measure MLJBase.jl -> StatisticalMeasures.jl (Address breaking changes in MLJBase 1.0 #21)
• Make the string representations of metrics on the MLflow service more informative. The value of the first parameter of the metric is now included in the representation (Address breaking changes in MLJBase 1.0 #21)

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/92417

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

[ablaom]

@JuliaRegistrator register branch=master

Release notes:

(breaking) Rename MLFlowLogger (exported) to Logger (unexported). So a logger instance is now instantiated with using MLJFlow; logger = MLJFlow.Logger(baseuri).

(testing) Facilitate local testing by adding MLFLOW_URI environment variable to set the location of the running MLflow service (#30)

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/95665

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

[pebeto]

@JuliaRegistrator register branch=master

Release notes:

(breaking) Removing healthcheck function on Logger() instantiation due to platforms inconsistency (see #34).

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/102489

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

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/102504

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

[pebeto]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Error while trying to register: Version 0.4.1 already exists

[pebeto]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/107098

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

[pebeto]

@JuliaRegistrator register branch=master

Release notes:

• [new feature] Added complete support with MLJ's TunedModel, being fully-compatible with accelerators (CPUThreads() and CPUProcesses()). This feature is not supported by mlflow, but implemented here following a Producer-Consumer pattern using a Channel approach.
• [fix] Logger is now a mutable struct, which means that its fields are modifiable outside instantiation.

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/107349

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

[pebeto]

@JuliaRegistrator register branch=master

Release notes:

• [breaking] Renaming _logging_channel to logging_channel, and changing its type from Channel{Tuple} to Union{Channel{Tuple}, Nothing}
• [breaking] open_logging_channel function now requires a Logger instance and doesn't return a Channel anymore. The reason is to keep logging_channel in a "private" form in our model
• [improvement] Removed non-useful wait!(result_channel) in src/base.jl
• [improvement] Explicitly closing the logging_channel when a result is retrieved in the background worker

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/107366

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