Skip to content

New package: PowerTableDataParser v1.0.0#153336

Merged
JuliaTagBot merged 1 commit intomasterfrom
registrator-powertabledataparser-2b750c0e-v1.0.0-7782196f72
Apr 23, 2026
Merged

New package: PowerTableDataParser v1.0.0#153336
JuliaTagBot merged 1 commit intomasterfrom
registrator-powertabledataparser-2b750c0e-v1.0.0-7782196f72

Conversation

@JuliaRegistrator
Copy link
Copy Markdown
Contributor

@JuliaRegistrator JuliaRegistrator commented Apr 20, 2026

JuliaRegistrator referenced this pull request in NLR-Sienna/PowerTableDataParser.jl Apr 20, 2026
@JuliaRegistrator JuliaRegistrator force-pushed the registrator-powertabledataparser-2b750c0e-v1.0.0-7782196f72 branch from 4eb9a6b to cbf2d1a Compare April 20, 2026 04:15
JuliaRegistrator referenced this pull request in NLR-Sienna/PowerTableDataParser.jl Apr 20, 2026
@github-actions
Copy link
Copy Markdown
Contributor

Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. New package registration

Please make sure that you have read the package naming guidelines.

2. AutoMerge Guidelines are all met! ✅

Your new package registration met all of the guidelines for auto-merging and is scheduled to be merged when the mandatory waiting period (3 days) has elapsed.

3. To pause or stop registration

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.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.

@JuliaRegistrator JuliaRegistrator force-pushed the registrator-powertabledataparser-2b750c0e-v1.0.0-7782196f72 branch from cbf2d1a to 533ea1b Compare April 20, 2026 04:28
@goerz
Copy link
Copy Markdown
Member

goerz commented Apr 20, 2026

Depending on your definition of "work in progress", "this repository contains a Work-in-progress version of the CSV Data Parser (CDM) from PowerSystems.jl" may contradict the release as a v1.0.0 version. More importantly, though, this package seems to lack documentation (the links to the GitHub pages are dead). If you are following semantic versioning, that would be a requirement for a 1.0 release. Similarly, you would want to fix the CI and code coverage tracking before making a release.

@JuliaTagBot JuliaTagBot added the AutoMerge: last run blocked by comment PR blocked by one or more comments lacking the string [noblock]. label Apr 20, 2026
UUID: 2b750c0e-0bff-11f1-9200-1befd75df6be
Repo: https://github.com/NLR-Sienna/PowerTableDataParser.jl.git
Tree: 9973b3791bcc08c1640aa1030ab07b300354280d

Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3
@JuliaRegistrator JuliaRegistrator force-pushed the registrator-powertabledataparser-2b750c0e-v1.0.0-7782196f72 branch from 533ea1b to 70ae703 Compare April 20, 2026 17:47
JuliaRegistrator referenced this pull request in NLR-Sienna/PowerTableDataParser.jl Apr 20, 2026
@jd-lara
Copy link
Copy Markdown
Contributor

jd-lara commented Apr 20, 2026

@goerz this package is an off shot from a pretty mature library and code base that hasn't changed in a while, the API is stable and it is already widely used in PowerSystems.jl.

I fixed the README, documentation and the code coverage is just waiting for a new run. [noblock]

@goerz
Copy link
Copy Markdown
Member

goerz commented Apr 20, 2026

Yeah, that's fine. I figured the "WIP" was more likely something that should be removed from the README, as you now did.

The link to the documentation still gives me a 404. You may have to enable GitHub pages in the settings, or something like that. As soon as that is fixed, and assuming that Documentation contains an API documentation, you should be good to go.

@jd-lara
Copy link
Copy Markdown
Contributor

jd-lara commented Apr 20, 2026

Yeah, that's fine. I figured the "WIP" was more likely something that should be removed from the README, as you now did.

The link to the documentation still gives me a 404. You may have to enable GitHub pages in the settings, or something like that. As soon as that is fixed, and assuming that Documentation contains an API documentation, you should be good to go.

The documentation builds https://nlr-sienna.github.io/PowerTableDataParser.jl/dev/ since there isn't a release the stable version points nowhere. Once there is a release the https://nlr-sienna.github.io/PowerTableDataParser.jl/stable will go to the 1.0.0 page in the gh-pages

@goerz
Copy link
Copy Markdown
Member

goerz commented Apr 20, 2026

Great, thanks. LGTM.

I'll just apply the "ignore blocking comments" override, since that's easier than both of use editing each comment to contain [noblock]. If, for whatever reason you (or anyone else) want to block registration within the remainder of the waiting period, make sure to @goerz me.

@goerz goerz added the Override AutoMerge: ignore blocking comments Instructs automerge to ignore blocking comments label Apr 20, 2026
@JuliaTagBot JuliaTagBot removed the AutoMerge: last run blocked by comment PR blocked by one or more comments lacking the string [noblock]. label Apr 20, 2026
@JuliaTagBot JuliaTagBot merged commit 79e74df into master Apr 23, 2026
23 checks passed
@JuliaTagBot JuliaTagBot deleted the registrator-powertabledataparser-2b750c0e-v1.0.0-7782196f72 branch April 23, 2026 04:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new package Override AutoMerge: ignore blocking comments Instructs automerge to ignore blocking comments

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants