Skip to content

Conversation

@JuliaRegistrator
Copy link
Contributor

  • Registering package: PiCLES
  • Repository: https://github.com/mochell/PiCLES
  • Created by: @mochell
  • Version: v0.1.0-DEV
  • Commit: 7315ca6b066a0c4c9eea61c5c7e96c146bb09520
  • Git reference: main
  • Description: Particle-In-CelL for Efficient Swell - An efficient surface wave model for Earth System Models
  • Release notes:
v0.1.0_DEV

UUID: 79df3bd2-fdbb-4cb7-a58f-f9c8092d6d68
Repo: https://github.com/mochell/PiCLES.git
Tree: 4f61059f551b3370f5fd5bc7a98d172459f36840

Registrator tree SHA: be588f25c435fa5b456b986adf2f5c02bd3298f2
@JuliaRegistrator JuliaRegistrator force-pushed the registrator-picles-79df3bd2-v0.1.0-DEV-d78471d496 branch from 7597e13 to 892785d Compare December 4, 2025 02:50
@github-actions
Copy link
Contributor

github-actions bot commented Dec 4, 2025

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 ❌

  • Repo URL does not end with /name.jl.git, where name is the package name

  • Version number is not allowed to contain prerelease data

  • The following dependencies do not have a [compat] entry that is upper-bounded and only includes a finite number of breaking releases: ArgParse, Atom, BenchmarkTools, CairoMakie, Callbacks, ColorSchemes, DataFrames, DataStructures, Dierckx, DifferentialEquations, DocStringExtensions, ForwardDiff, GEMPIC, GLMakie, GeoMakie, HDF5, IfElse, Interpolations, JLD2, Juno, LaTeXStrings, Makie, NCDatasets, Oceananigans, OrderedCollections, Pandas, Parameters, PkgTemplates, Plots, ProfileView, PyCall, PyPlot, Revise, Setfield, StaticArrays, StructArrays, UnicodePlots, WebIO

    Extended explanation

    Your package has a Project.toml file which might look something like the following:

    name = "YourPackage"
    uuid = "random id"
    authors = ["Author Names"]
    version = "major.minor"
    
    [deps]
    # Package dependencies
    # ...
    
    [compat]
    # ...

    Every package listed in [deps], along with julia itself, must also be listed under [compat] (if you don't have a [compat] section, make one!). See the Pkg docs for the syntax for compatibility bounds, and this documentation for more on the kinds of compat bounds required for AutoMerge.

  • I was not able to install the package (i.e. Pkg.add("PiCLES") failed). See the AutoMerge logs for details.

  • I was not able to load the package (i.e. import PiCLES 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.

3 participants