Register on General

[korenmiklos]

@JuliaRegistrator register()

[JuliaRegistrator]

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

[korenmiklos]

@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/110353

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

Also, note the warning: This looks like a new registration that registers version 0.4.1.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
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.

[korenmiklos]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/110353

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

Also, note the warning: This looks like a new registration that registers version 0.4.1.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
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.

[korenmiklos]

I added a compat string to RDatasets

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/110353

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

Also, note the warning: This looks like a new registration that registers version 0.4.1.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
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.

[korenmiklos]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/110398

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>" 3305cff28c43e3949edec2542daa70d9d5f61f38
git push origin v0.4.3

Also, note the warning: This looks like a new registration that registers version 0.4.3.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
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.

[korenmiklos]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/110740

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.5 -m "<description of version>" 6faf5f61bbf639965637766840b014cb341b26af
git push origin v0.4.5

Also, note the warning: Version 0.4.5 skips over 0.4.4
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.

[korenmiklos]

@JuliaRegistrator register

[JuliaRegistrator]

Error while trying to register: Version 0.4.5 already exists

[korenmiklos]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/110815

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

[korenmiklos]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/110934

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.7 -m "<description of version>" 88bb0044ddf8b8cd4c47bf8c10ee63313637a7d8
git push origin v0.4.7

[korenmiklos]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/111110

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.8 -m "<description of version>" 26aae122acd18d4534977afabbe2342c4ca0788f
git push origin v0.4.8

[korenmiklos]

@JuliaRegistrator register

Release notes:

Summary

New features implemented:

• @clear
• @use "fname.dta", clear
• @describe
• @list varlist
• ~f(x) to stop vectorization of f()
• cond() function
• display Kezdi.jl command
• bugfixes

Related Issues

• fixes feat: @clear as setdf(nothing) #117
• fixes feat: option clear to @use #118
• fixes feat: @describe #121
• fixes feat: @list should allow for columns #131
• fixes bug: allow ternary operator in expressions #146
• fixes feat: display command #147
• fixes bug: _n cannot be both in arguments and in if #158
• fixes feat: change DNV to ~ to be consistent with Tidier.jl #161
• fixes feat: use Main.x to refer to variable in Main? #162
• fixes docs: explain how variables other than df columns can be used in Kezdi.jl #165
• fixes bug: replace does not find user-defined function? #182

Number of Passing Unit Tests

Tests passing: 425/425

Checklist

• Version number has been bumped in Project.toml

Tests

• ] test runs without errors
• Unit tests have been added
• This is a refactoring, no new tests required

Documentation

• Documentation has been updated
• No change to public API, documentation not required

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/111838

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

Also, note the warning: Version 0.5.1 skips over 0.5.0
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.

[gergelyattilakiss]

@JuliaRegistrator register

Release notes:

Summary

• For generate, egen and replace, removed setdf from the end to avoid copying the entire df.
• Fixed a critical bug, bug: replace does not find user-defined function? #182
• Implement @mvencode (feat: mvencode #176)
• Implement @save (feat: @save for saving .dta files #179)

Related Issues

Number of Passing Unit Tests

474/474

Also see test/speed.jl (I should turn this into a unit test!)

Checklist

• Version number has been bumped in Project.toml

Tests

• ] test runs without errors
• Unit tests have been added
• This is a refactoring, no new tests required

Documentation

• Documentation has been updated
• No change to public API, documentation not required

New features implemented in the API and updated speed benchmarks.

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/115869

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

[gergelyattilakiss]

@JuliaRegistrator register

Release notes:

Summary

• Fixed compatibility issue with 1.11 Julia
• Implement @reshape

Related Issues

• feat: reshape #172
• debug compatibility with Julia 1.11 #195

Number of Passing Unit Tests

520/520

Checklist

• Version number has been bumped in Project.toml

Tests

• ] test runs without errors
• Unit tests have been added
• This is a refactoring, no new tests required

Documentation

• Documentation has been updated
• No change to public API, documentation not required

New features implemented in the API.

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/119493

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.3 -m "<description of version>" 97359807613840d73f20fb33825293a192785e84
git push origin v0.5.3

[korenmiklos]

@gergelyattilakiss please add a compat entry for julia