New release

[JackDevine]

A lot has happened on master since v0.4.0 and some of it is slightly breaking, so we should definitely make a new release.

Summary of changes made:

• Each edge has its own series: [RFC] Add different line width for each edge GraphRecipes.jl#57
• Edge labels can be specified through the edgelabel kwarg Add edge labels GraphRecipes.jl#65
• Directed graphs can now be handled and have arrows WIP Directed edges GraphRecipes.jl#67
• Nodes are no longer Plots.jl markers. Meaning that markershape and markersize are now replaced with nodeshape and nodesize WIP Directed edges GraphRecipes.jl#67
• Graphs with self edges can be visualized Add self edges GraphRecipes.jl#68
• Mulitgraphs can be visualized and edgelabels accepts triples to specify the labels WIP: Multigraphs GraphRecipes.jl#71
• Many of the keyword arguments to grahplot have aliases Add aliases for keyword arguments GraphRecipes.jl#88

Issues to be fixed before new release:

• Different nodeshape in tree graph #5342
• Minimal example gives nonsense. #5349
• Add aliases for kwargs #5344
• Node scaling issues #5345

I may add to the list and I am open for suggestions to add to the list. I believe that the fact that we have moved away from Plots.jl markers warrants a major release (upgrade to v0.5.0). Fixing #5344 will slightly improve things, however, ultimately, we have made a break from the old GraphRecipes in JuliaPlots/GraphRecipes.jl#67.

In the meantime, the README gives incorrect results for people who are not on master (see #5341). I guess that nobody expected the new release to take this long. Perhaps we should put a warning on the readme? Not sure. EDIT: Fixed in JuliaPlots/GraphRecipes.jl#88

[mkborregaard]

This is awesome. Makes sense to put a small ("note: this currently requires the master branch") in the readme. I definitely agree we should push a 0.5.0 versino

[NHDaly]

Looking forward to a new release here! :) <3

Since all the cited Issues have been fixed, is there anything else remaining to be done before a release can be tagged?
Thanks!

[mkborregaard]

Agreed - I prefer to let @JackDevine do the honors though if you've got the time? Given that you're responsible for all these awesome fixes 💖

[JackDevine]

I have been struggling to find a good time to do this. Fingers crossed I should be able to do it tomorrow evening (New Zealand time).

Thanks for the kind words everyone! :)

[JackDevine]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/8596

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 Julia TagBot is installed, or can be done manually through the github interface, or via:

git tag -a v0.5.0 -m "<description of version>" c2690e6f55838fc732be641d5921b85b72a5d870
git push origin v0.5.0

[JackDevine]

The tagbot was clever enough to notice a certain lack of upper bounds. I think that I have solved the problem now. In any case, we probably need a better solution than just manually entering upper bounds in the Project.toml. I think that the CompatHelper recommended by the bot is a good way of doing things.

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/8596

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 Julia TagBot is installed, or can be done manually through the github interface, or via:

git tag -a v0.5.0 -m "<description of version>" 80dedd7ef2286474c5a0c96c2038826912c237c3
git push origin v0.5.0

[mkborregaard]

Yes. @daschw is compathelper not activated for this repo? It is for most other JuliaPlots repos I think.