Skip to content

New package: DiscoveryGraph v0.2.0#149721

Closed
JuliaRegistrator wants to merge 1 commit intomasterfrom
registrator-discoverygraph-6c26c9e7-v0.2.0-7c85d7f0ab
Closed

New package: DiscoveryGraph v0.2.0#149721
JuliaRegistrator wants to merge 1 commit intomasterfrom
registrator-discoverygraph-6c26c9e7-v0.2.0-7c85d7f0ab

Conversation

@JuliaRegistrator
Copy link
Contributor

UUID: 6c26c9e7-0ef1-44eb-bb5c-4a6256936300
Repo: https://github.com/technocrat/DiscoveryGraph.jl.git
Tree: 43cfe50b9fafdafda6419ec7140a16fdaecbb3c8

Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3
JuliaRegistrator referenced this pull request in technocrat/DiscoveryGraph.jl Mar 3, 2026
New features since 0.1.0:
- RegulatoryAdvisor CounselType variant and Enron regulatory_affairs role
- Outside counsel privilege gap fix (_addr_counsel_roles pattern-matching)
- XLSX config helper (write_config_template / config_from_xlsx)
- Leiden seed + resolution in DiscoverySession and Rule 26(f) memo
- Bot/broadcast filter audit section in memo
- Hotbutton keyword provenance labeling
- Counsel detection transparency (explicit vs auto-detected split)
- Schema versioning (schema_version field on CorpusConfig)
- ferc/sec moved to ENRON_TIER1_EXAMPLES (DEFAULT_TIER1_KEYWORDS now matter-independent)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions
Copy link
Contributor

github-actions bot commented Mar 3, 2026

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 which are not met ❌

  • I was not able to install the package (i.e. Pkg.add("DiscoveryGraph") failed). See the AutoMerge logs for details.
  • No licenses detected in the package's top-level folder. An OSI-approved license is required.
  • I was not able to load the package (i.e. import DiscoveryGraph failed). See the AutoMerge logs for details.

3. Needs action: here's what to do next

  1. Please try to update your package to conform to these guidelines. The General registry's README has an FAQ that can help figure out how to do so.
  2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless the AutoMerge issue is that you skipped a version number).

If you need help fixing the AutoMerge issues, or want your pull request to be manually merged instead, please post a comment explaining what you need help with or why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the public Julia Slack for better visibility.

4. 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.

@goerz
Copy link
Member

goerz commented Mar 4, 2026

Closing in favor of #149739

Please avoid changing the version number when fixing automerge issues. That way, the Registrator updates the existing PR instead of creating a new one.

@goerz goerz closed this Mar 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants