Repository navigation
Issue to trigger new releases #2
Description
Activity
@JuliaRegistrator register
Registration pull request updated: JuliaRegistries/General/32747
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>" 9e441349a178cae97943240fe45f47b3d3afd9ea git push origin v0.1.0@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/33056
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>" 288efa7ea1e7e94877383f65ccecc4f2360890d4 git push origin v0.1.1@JuliaRegistrator register
release notes:
- (breaking) Change default value of
finWithIterationsDo(f=...)tof(i) = @info("num iterations: $i") - (breaking) Remove
Savecontrol (now moved to MLJSerialization)
- (breaking) Change default value of
Registration pull request created: JuliaRegistries/General/33299
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>" 58027f2680ec309632c2a251d189bbc964315df1 git push origin v0.2.0@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/33706
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.1 -m "<description of version>" 863198180a5af044428342a5cb459198637aa83d git push origin v0.2.1@JuliaRegistrator register
release notes:
- Some more informative logging (Make it clearer in docs that one control must be a training control #11, Add warning for use of shuffling in holdout #13)
Registration pull request created: JuliaRegistries/General/33810
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.2 -m "<description of version>" 452f63af6c268f982bdbef3a30fd070bd32c9496 git push origin v0.2.2@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/34965
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.3 -m "<description of version>" c488ecdb74f4148fc5274d516fd9cbeed91ad2af git push origin v0.2.3@JuliaRegistrator register
release notes:
- Update control API to IterationControl 0.4, which has a new signature for
IterationControl.update!(control, ...).
- Update control API to IterationControl 0.4, which has a new signature for
Registration pull request created: JuliaRegistries/General/35094
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>" 5943532ad7e54fb844e4c36159b1595bc1da6dac git push origin v0.3.0@JuliaRegistrator register
release notes:
- Remove warning about slow down for
Holdout(rng=...)as no longer applicable. Allow user to explicitly specify a train/test holdout set (of row indices), as inresampling = [(train, test), ]for some integer vectorstrainandtest(as inevaluate!) ( Issue warning if shuffling the Holdout sample #12, Remove warnings whenresampling=Holdout(rng=...)#22)
- Remove warning about slow down for
21 remaining items
Registration pull request created: JuliaRegistries/General/58002
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>" 6ae311f48919203a7a680b8b51f0f3f6c296091c git push origin v0.5.0@JuliaRegistrator register branch=master
Registration pull request created: JuliaRegistries/General/71799
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>" 620a91fb6c9ed9bdeb2c2f5d72ca52dfc1f0869a git push origin v0.5.1@JuliaRegistrator register branch=master
Release notes:
-
(breaking) Bump compatibility requirement for MJBase to version 1. When using without MLJ, users may need to explicitly import StatisticalMeasures.jl. See also the MLJBase 1.0 migration guide (Adapt tests broken by migration of measures MLJBase.jl -> StatisticalMeasures.jl #56)
-
(breaking) In the default control, use
Step(1)instead ofStep(10)(SubstituteStep(1)in place ofStep(10)incontrolsdefault #49)
-
Registration pull request created: JuliaRegistries/General/92207
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.6.0 -m "<description of version>" 711132fe56cb6f27f79ca2739b31c26141233810 git push origin v0.6.0@JuliaRegistrator register branch=master
Registration pull request created: JuliaRegistries/General/102483
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 - blahTo 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.6.1 -m "<description of version>" 4de6d325bebca3713daa8f255222b940e5824efe git push origin v0.6.1@JuliaRegistrator register branch=master
Registration pull request created: JuliaRegistries/General/108128
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 - blahTo 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.6.2 -m "<description of version>" 387c7c24e08bfd5114bbd2dda6934816a5b0de3d git push origin v0.6.2@JuliaRegistrator register branch=master
Release notes:
- Allow models that report feature importances to be wrapped in
IteratedModeland have the wrapper also support feature importances (feature_importancesdoesn't work in iterated model #66)
- Allow models that report feature importances to be wrapped in
Registration pull request created: JuliaRegistries/General/114625
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.6.3 -m "<description of version>" db93024deda696bf92416de23740eb217d4cc728 git push origin v0.6.3@JuliaRegistrator register branch=master
Registration pull request created: JuliaRegistries/General/141868
Recommendation: add release notes
Release notes help your users know what has changed in the new version. For breaking releases in particular, it's recommended to document what breaking changes were made (or point to where changes can be found, such as a changelog).
To add release notes, 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 - blahTo add release notes to this registration, just re-invoke JuliaRegistrator 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.6.4 -m "<description of version>" e48996e5e79db326604f2a7224090d1d083f79f1 git push origin v0.6.4@JuliaRegistrator register branch=master
Release notes:
(new feature) Add logger support for
IteratedModelinstances, for live logging of the out-of-sample loss to, eg, an mlflow service (using MLJFlow.jl).(#74)Registration pull request created: JuliaRegistries/General/155228
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.6.5 -m "<description of version>" 6312eec02cfb37f2ca94d6fd5afc639d80775994 git push origin v0.6.5
@JuliaRegistrator register