Skip to content

New package: JuliaLibWrapping v0.1.0#156889

Open
JuliaRegistrator wants to merge 1 commit into
masterfrom
registrator-julialibwrapping-d61f35a8-v0.1.0-9b1d16c9e7
Open

New package: JuliaLibWrapping v0.1.0#156889
JuliaRegistrator wants to merge 1 commit into
masterfrom
registrator-julialibwrapping-d61f35a8-v0.1.0-9b1d16c9e7

Conversation

@JuliaRegistrator
Copy link
Copy Markdown
Contributor

UUID: d61f35a8-f6af-436f-bc10-cee6b101f7bd
Repo: https://github.com/JuliaInterop/JuliaLibWrapping.jl.git
Tree: 47641fcfb644e7a5d962ed325e32f090a2c715eb

Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3
JuliaRegistrator referenced this pull request in JuliaInterop/JuliaLibWrapping.jl Jun 2, 2026
Move the main package from the repo root into a JuliaLibWrapping/ subdir,
sibling to the existing JLWInterop/. Previously the main package sat at the
root and contained JLWInterop/, so the registered JuliaLibWrapping source tree
would have shipped an unused copy of JLWInterop. Each subdir package now also
carries its own LICENSE, as the General registry requires for subdir packages.

- Move src/ ext/ test/ docs/ examples/ Project.toml README.md under
  JuliaLibWrapping/; add a short monorepo README at the root.
- Fix the relative paths that crossed the moved boundary: examples/ols/build.jl
  (../../JLWInterop -> ../../../JLWInterop) and docs/Project.toml (JLWInterop
  source path; also add JuliaLibWrapping as a [sources] path so the docs env is
  self-contained). The build-env [sources] and test->examples paths move as a
  unit and stay valid.
- Re-prefix the root-anchored .gitignore entries.
- Rework CI to test both packages via a package matrix (setup-julia's project
  input resolves each package's own min), deploy docs from the subdir via a
  manual make.jl run, and point TagBot/CompatHelper at the subdir packages.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 2, 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 ❌

  • Lowercase package name julialibwrapping contains the string "julia".
  • I was not able to install the package (i.e. Pkg.add("JuliaLibWrapping") failed). See the AutoMerge logs for details.
  • I was not able to load the package (i.e. import JuliaLibWrapping 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.

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