New package: SpinSim v0.0.1

[JuliaRegistrator]

• Registering package: SpinSim
• Repository: https://github.com/javinoram/SpinSim.jl
• Created by: @javinoram
• Version: v0.0.1
• Commit: 2834c2119744ff75dc9f4b7062c1771146c194fb
• Reviewed by: @javinoram
• Reference: release v0.0.1 javinoram/SpinSim.jl#4 (comment)
• Description: Julia package to simulate and study spin models

[github-actions]

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 ❌

• There is no compat entry for julia.

• The following dependencies do not have a [compat] entry that is upper-bounded and only includes a finite number of breaking releases: Documenter, TestItemRunner

  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.

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]

Thank you for submitting your package! However, please make sure that it has documentation and tests before registering.

[javinoram]

Sure, when I had the documentation and some more code, I will upload again.

[goerz]

We can just keep this open. You can retrigger the registration to update this PR when you’re ready [noblock]

[javinoram]

Hi, I received an email with the bot’s message, recently I didn't have some much time to work in the project, so what should I do? if the PR get closed, can I retriggered?

[goerz]

[noblock] Yes, if it gets closed (but it won’t for another 30 days now, at least), you can just re-register it at any point in the future, and it will just be a new PR

[javinoram]

thanks

[javinoram]

Hi, it's me again, sorry to bother you again, I upload a new version with more code (the last month, I forget to ask here) and I was wondering if now it can be merged or I'm missing something else, thank you in advance

[goerz]

Yeah, seems okay now. It wouldn't be a bad idea to copy the introduction paragraph into the README, and also a link to the full documentation (most packages use "badges" as documentation links).

Since this PR is now quite out-of-date, and just to make sure that the version that gets registered is the current version, I would recommend setting the version to 0.1.0 at this point and to redo the registration. That'll create a new PR which then should auto-merge after three days. I'll close this PR once the new one is online.

[javinoram]

Sure, thanks.

[goerz]

Closing in favor of #120062