Register as official Julia package name

[iago-lito]

See instructions at https://github.com/JuliaRegistries/General. Blocked on #105.. unblocked.

• [x] Request registration.
• [x] Wait on registration to be effective.
• [x] Update install procedure in the README.

[iago-lito]

Wait on #147 to land to issue a proper v0.2.0 release first :)

[iago-lito]

Unblocked! Let's do this :D

[iago-lito]

So, is this how that works?

@JuliaRegistrator register tag=v0.2.0

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/103413

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

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

[iago-lito]

Wops, we never had [compat] sections so far. Fixed that. Force-pushed to main and relocated tag v0.2.0.

@JuliaRegistrator register tag=v0.2.0

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/103413

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

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

[iago-lito]

Good. Let's wait on JuliaRegistries/General/103413 to be accepted then :)

[iago-lito]

Accepted! ] add EcologicalNetworksDynamics should work anywhere now :)