Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New package: VOPLS v0.0.1-DEV #122105

Conversation

JuliaRegistrator
Copy link
Contributor

@JuliaRegistrator JuliaRegistrator commented Dec 28, 2024

# VOPLS.jl v0.1.0-DEV Release Notes

We are excited to announce the first release of **VOPLS.jl**, a Julia package for solving vector optimization problems using line search methods. Please note that this package is under heavy development, and significant updates are expected in future releases.

## Key Features

- **Line Search Methods**: Initial implementation of algorithms for vector optimization problems.
- **Multiobjective Optimization**: Basic support for solving problems with multiple objectives.

## Installation

To install VOPLS, use Julia's package manager:

```julia
using Pkg
Pkg.add("VOPLS")
```



Thank you for exploring VOPLS.jl!

@mmogib
Copy link

mmogib commented Dec 28, 2024

This is the first commit. Accepted

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

  • Name does not meet all of the following: starts with an upper-case letter, ASCII alphanumerics only, not all letters are upper-case.
  • Version number is not allowed to contain prerelease data

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.

@JuliaTagBot JuliaTagBot added the AutoMerge: last run blocked by comment PR blocked by one or more comments lacking the string [noblock]. label Dec 28, 2024
UUID: 11323060-fdcc-4929-8e2b-ee81bb1296f8
Repo: https://github.com/mmogib/VOPLS.jl.git
Tree: 1962b71ba5931bf377718f7270130edcc69f90ec

Registrator tree SHA: 191228b6dd8b9d0e2965ae3e705fe54c51dcfee8
@JuliaRegistrator JuliaRegistrator force-pushed the registrator-vopls-11323060-v0.0.1-DEV-5862d9eb16 branch from 64de94a to c43939e Compare December 28, 2024 07:09
@GunnarFarneback
Copy link
Contributor

I'm going to close this registration request since the package doesn't have any content beside the README, see https://github.com/JuliaRegistries/General?tab=readme-ov-file#should-i-register-my-package-now.

Feel free to resubmit once the package has some real substance.

Then there are the automerge complaints:

  1. Name does not meet all of the following: starts with an upper-case letter, ASCII alphanumerics only, not all letters are upper-case.
  2. Version number is not allowed to contain prerelease data

The first can be addressed either by renaming the package (recommended) or by convincing someone with merge rights in this repository (I'm not one of them) that it should be accepted. The second complaint can be fixed simply by not having a -DEV or similar in the version being registered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AutoMerge: last run blocked by comment PR blocked by one or more comments lacking the string [noblock]. new package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants