Registration to the Julia general registry

[grasph]

@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/101684

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 v1.1.1 -m "<description of version>" 5f6f40a4726702042261c0b1ae974ba17ca10aa3
git push origin v1.1.1

Also, note the warning: This looks like a new registration that registers version 1.1.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.

[grasph]

@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/101684

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 v1.1.1 -m "<description of version>" 3523839348659a295e3f37d4a8df242830106ec3
git push origin v1.1.1

Also, note the warning: This looks like a new registration that registers version 1.1.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.

[grasph]

@JuliaRegistrator register

Release notes:

See https://github.com/grasph/wrapit/releases/tag/v1.3.0.

In addition, wrapit() returns now the underlying wrapit command exit code only if the returncode keyword argument is set to true. That prevents the confusing number shown in REPL when executing the command. The return code was always 0 in case of a termination by a signal, it is now the correct code.

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/103639

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 v1.3.1 -m "<description of version>" c1c6de5e4ac431f59b1f7063bc9e6911ae8d66e3
git push origin v1.3.1

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

[grasph]

@JuliaRegistrator register

Release notes:

See https://github.com/grasph/wrapit/releases/tag/v1.3.2

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/108416

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 v1.3.2 -m "<description of version>" f0dd3baebe83ab8b542010249e8d69b8d1334ec6
git push origin v1.3.2

[grasph]

@JuliaRegistrator register

Release notes:

See https://github.com/grasph/wrapit/releases/tag/v1.3.3

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/109611

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 v1.3.3 -m "<description of version>" 4f90809bfe4cf368c17adc7e69c617f1067a9050
git push origin v1.3.3

[grasph]

@JuliaRegistrator register()

[JuliaRegistrator]

Error while trying to register: Version 1.3.3 already exists

[grasph]

@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/111987

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 v1.4.0 -m "<description of version>" 3e883db799fad99aac6be90b9319e89b21314340
git push origin v1.4.0

[grasph]

@JuliaRegistrator register

Release notes:

See https://github.com/grasph/wrapit/releases/tag/v1.4.0.

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/111987

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 v1.4.0 -m "<description of version>" 3e883db799fad99aac6be90b9319e89b21314340
git push origin v1.4.0