Issue to trigger new releases

[ablaom]

Procedure for new releases:

• merge new contributions onto dev (the base branch for PR's, by default)
• bump version on dev
• make a new PR dev -> master with the title like "For a 0.2.5 release" with list of PR's since last release, and merge if passing
• make a new comment below to trigger a PR to General (see examples below) including release notes if appropriate (always the case if there are breaking changes). Again, see examples below. Alternatively, release notes can be edited after TagBot does it's thing.

[ablaom]

JuliaRegistries/General#60310

[ablaom]

@JuliaRegistrator register branch=master

Release notes:

• (enhancement) Add method wrap which allows one to wrap a decision tree (Leaf or Node object) in a new tree structure implementing the AbstractTrees.jl interface. Unlike raw DecisionTree.jl decision trees, the nodes of the wrapped objects can include the names of splitting-features at nodes, and any other node metadata. See the wrap docstring for details. (Add implementation of AbstractTrees-interface #158) @roland-KA

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/60432

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.12 -m "<description of version>" 7e090bbf7536f3aa8871bb3ac36bfe9ff815ab90
git push origin v0.10.12

[ablaom]

@JuliaRegistrator register branch=master

Release notes:

• (bug fixes) Ensure nfoldsCV passes the RNG on to AdaBoostClassifier models. Fix non-threadsafe use of RNGs in random forests (Test multiple seeds #174) @rikhuijzer
• (testing) Replace all RNGs in tests with StableRNGs to ensure consistency across Julia versions and introduce tests over multiple seeds (Test multiple seeds #174) @rikhuijzer
• (enhancement) Improve display returned by print_tree (making it consistent with the AbstractTrees.jl fallback) and fix docstring (Fix typo in print_tree description #171, Replace L by < and R by ≥ #172, Round digits in print_tree #173) @rikhuijzer

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/62827

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.13 -m "<description of version>" 66f99b8a4645791e84b46f5d766a79107a0e1443
git push origin v0.10.13

[ablaom]

@JuliaRegistrator register branch=master

Release notes:

• Bump minimum Julia version to 1.6.
• (enhancement) Add methods impurity_importance, split_importance and permutation_importance for all models (Feature importance #182) @yufongpeng
• (breaking) Use the SAMME algorithm for calculating AdaBoostStumpClassifier coefficients (Adabooststump algorithm change #167) @yufongpeng
• (breaking) Do not export the functions R2, mean_sqaure_error, majority_vote, confusion_matrix and ConfusionMatrix (Stop exporting measures #183)
• Add accuracy to built-in measures but do not export.

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/63455

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>" 9eb6ad9ebcc465d4141c582aa47e7aa89030778d
git push origin v0.11.0

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/63725

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>" 1cdbbbe64d28291bff66a0bd17e85d4d2f71b7d2
git push origin v0.11.1

[ablaom]

@JuliaRegistrator register branch=master

Release notes:

• (enhancement) Add option to use multithreading in getting predictions for random forests, as in apply_forest(forest, features; use_multithreading=true). The default continues to be no threading. (Multithreading for random forest predictions #188) @salbert83

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/64436

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>" 38dbbb8a6e0ca5ab1e7ef5b1b6c4a5e1667a1ac2
git push origin v0.11.2

[ablaom]

@JuliaRegistrator register branch=master

Release notes:

• (enhancement) Adapt to new AbstractNode in AbstractTrees #195 @roland-KA

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/72785

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

[ablaom]

@JuliaRegistrator register branch=master

Release notes:

• (breaking) For each tree in a random forest models, use seed! to put a copy of each associated RNG into a unique state, to mitigate observed correlation between trees (RNG “shuffling” introduced in #174 is fundamentally flawed #194, Use seed! to put every copy of rng into a unique state #198) @dhanak @rikhuijzer

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/73106

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.12.0 -m "<description of version>" 5a04abaa9f355190ae5f0b3a5fd76e88d3246d2c
git push origin v0.12.0

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/73617

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

[ablaom]

@roland-KA Above includes your recent PR #200 .

[ablaom]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/75351

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.12.2 -m "<description of version>" 0854fb0652c68b9bd1c5e8fe678a8bec763794aa
git push origin v0.12.2

[ablaom]

@JuliaRegistrator register branch=master-0.11.4

[JuliaRegistrator]

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

[ablaom]

@JuliaRegistrator register branch=master-0.11.4

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/75353

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.4 -m "<description of version>" 3baed2e151f394dd40405ea096215d3f08e40440
git push origin v0.11.4

[ablaom]

@JuliaRegistrator register branch=master

• (new feature) Allow build_forest(model, features, labels, options...; kwoptions...) -> enlarged_model to add trees to an existing model (Add method build_forest(model, ...) to add trees to existing model #216)

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/77611

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.12.3 -m "<description of version>" 85cd1247e3b3cd51f5b5537cba89b6c77f07d27e
git push origin v0.12.3

[rikhuijzer]

@JuliaRegistrator register branch=master

Release notes:

• (bugfix) This release fixes a bug where labels would internally always be converted to Float64 (Float64 replaced by AbstractFloat for regression #226). This is now fixed thanks to @xinadi!

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/93471

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.12.4 -m "<description of version>" 8314ad0b070910f72096827e6c844e873136ac23
git push origin v0.12.4