0.0.91 Release

[emmaccode]

I am thinking this release is likely going to the registry. I was hoping it would be the last one, but I am happy it will be this one because this release really polishes up the last few things Olive needs. Going forward, the big upgrades will primarily come in the form of new features and performance updates, aside from the next step to 0.0.92 reworking the project explorer. Exciting!

[emmaccode]

93, #116, and #115 will close this.

[emmaccode]

Ok, just #93, then some more doc/README work :)

hopefully finishing the README?

[emmaccode]

Oh, let's also go ahead and get rid of #103 !

[emmaccode]

Okay, now just

Ok, just #93, then some more doc/README work :)

hopefully finishing the README?

now just this :) <3

[emmaccode]

ok, finished #93 -- and a lot of other things -- pretty nice build. Going to write some more documentation, need to do updates to ToolipsSession and ToolipsMarkdown :)

[emmaccode]

Did not mean to close this -- oops

Ok so now we wait for the next version of ToolipsSession because we will want this to come first, then I will be registering this new version!

[emmaccode]

@JuliaRegistrator register Release notes:

performance

• improved memory usage
• removed directory cells from memory
• improved callback parsing with readonly

  cells

• moved styles to stylesheet
• overhauled markdown cells
• restyled base cells

The biggest changes here revolve around general stability, usability, and performance.

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/95085

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.0.91 -m "<description of version>" 1fb1ea62bb45455a1937192192dcb16489fc0a67
git push origin v0.0.91

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

[emmaccode]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/95085

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

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

[emmaccode]

ok, waiting on this version to register -- I have just registered ToolipsMarkdown 0.1.4, which includes the highlighting updates I was talking about above. nice. Once this registers, I will close this :) <3

[emmaccode]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/95085

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

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

[emmaccode]

:) merged