Issue for triggering new releases

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/38617

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.0 -m "<description of version>" 1180e1870569503c15b2deee646ff31974a7b1b7
git push origin v0.1.0

[ablaom]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/38617

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.0 -m "<description of version>" 09c43eb537a08b2a9eaae9f745eb06654d2b150b
git push origin v0.1.0

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/39928

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>" 89399da6200c32bc7bb6b5459457663af4c1fa17
git push origin v0.1.1

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/42686

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

[ablaom]

@JuliaRegistrator register branch=master

release notes:

• (breaking) Change syntax EnsembleModel(atom=...) to EnsembleModel(model=...) for consistency with other MLJ model wrappers (eg, TunedModel) but additionally allow passing model as non-keyword argument, as in EnsembleModel(my_tree, ...).
• Add CategoricalDistributions.jl as a dependency
• Bump compat for MLJBase to 0.19 and address the fact that UnivariateFinite functionality is not defined in MLJBase 0.19, but in CategoricalDistributions.jl instead.

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/51307

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>" 88cd6d40d8e09e10d1e49ea2bb5e0ab54373e68a
git push origin v0.2.0

[ablaom]

@JuliaRegistrator register branch=master

Release notes:

• (enhancement, breaking) Adapt to MLJBase 0.20, and in particular the new serialization API, which allows serialisation of EnsembleModel(model=...) where model is not necessarily a pure-Julia model (add serialization of ensembles #15) @olivierlabayle
• (bug fix) Enable safe wrapping of atomic models that implement a data front-end (fix data front-end bug #16 #17) @OkonSamuel

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/57999

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>" b8b3841cf85de0f2ca7ee0555f013e0faeb7bae3
git push origin v0.3.0

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/61929

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.1 -m "<description of version>" 09518b2d1cf211e940d537a15fd6c05e08963838
git push origin v0.3.1

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/71788

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

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/83149

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.3 -m "<description of version>" 43f74c1774145da50e70522fccee71693ce05b35
git push origin v0.3.3

[ablaom]

@JuliaRegistrator register branch=master

Release notes:

• (breaking) Remove MLJBase as dependency, replacing it with StatisticalMeasuresBase.jl. Adapt code appropriately to the new measures API. To use MLJEnsembles.jl without MLJBase.jl, one may need to explicitly import StatisticalMeasures.jl. See also the MLJBase 1.0 migration guide for further details (Adapt to migration of measures MLJBase -> StatisticalMeasures #30).

[JuliaRegistrator]

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

[ablaom]

@JuliaRegistrator register branch=master

Release notes:

• (breaking) Remove MLJBase as dependency, replacing it with StatisticalMeasuresBase.jl. Adapt code appropriately to the new measures API. To use MLJEnsembles.jl without MLJBase.jl, one may need to explicitly import StatisticalMeasures.jl. See also the MLJBase 1.0 migration guide for further details (Adapt to migration of measures MLJBase -> StatisticalMeasures #30).

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/92202

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>" 6ab6c66955677ad4b84a173fb0ff5a7b082c1a17
git push origin v0.4.0

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/105140

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>" af03f161f7482d0f87d686d063d97bbe80ba1e82
git push origin v0.4.1

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/106518

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>" 97122c3582b0cb02bb3ea1e5b3c7667e3610eb04
git push origin v0.4.2

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/108127

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