New package: TZJData v0.0.1+2023c

[JuliaRegistrator]

• Registering package: TZJData
• Repository: https://github.com/JuliaTime/TZJData.jl
• Created by: @omus
• Version: v0.0.1+2023c
• Commit: b6536d51e95a339fa12f984590f6c6cd45241300
• Reviewed by: @omus
• Reference: JuliaTime/TZJData.jl@b6536d5#commitcomment-123729804

[github-actions]

Your new package pull request does not meet the guidelines for auto-merging. Please make sure that you have read the General registry README and the AutoMerge guidelines. The following guidelines were not met:

• Version number is not allowed to contain build data

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.

After you have fixed the AutoMerge issues, simple retrigger Registrator, which will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number).

If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the Julia Slack to ask for help. Include a link to this pull request.

Since you are registering a new package, please make sure that you have also read the package naming guidelines: https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1

---

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment. You can edit blocking comments, adding [noblock] to them in order to unblock auto-merging.

[omus]

[noblock] Expecting AutoMerge to fail here due to including build metadata in the version. I've added some details about this in https://github.com/JuliaTime/TZJData.jl#versioning. The gist is that the build metadata appears to be the best way inform interested users which tzdata version is being used (tzdata versions are incompatible with semver) while still utilizing semver correctly. In the future I'll attempt to add an exception in RegistryCI.jl for this package to avoid the AutoMerge headache but as of this moment it would be good to get this release in to validate that nothing else in the registry machinery is going go choke on a non-JLL build number.