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.

Sign up for GitHub

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

Jump to bottom

Do not force creation of _cargo-index repo on publish (#27266) #27765

Merged
merged 1 commit into from
Oct 24, 2023
Merged

Do not force creation of _cargo-index repo on publish (#27266) #27765

merged 1 commit into from
Oct 24, 2023

Commits on Oct 24, 2023

  1. Do not force creation of _cargo-index repo on publish (go-gitea#27266) 

    Hello there,
Cargo Index over HTTP is now prefered over git for package updates: we
should not force users who do not need the GIT repo to have the repo
created/updated on each publish (it can still be created in the packages
settings).

The current behavior when publishing is to check if the repo exist and
create it on the fly if not, then update it's content.
Cargo HTTP Index does not rely on the repo itself so this will be
useless for everyone not using the git protocol for cargo registry.

This PR only disable the creation on the fly of the repo when publishing
a crate.

This is linked to go-gitea#26844 (error 500 when trying to publish a crate if
user is missing write access to the repo) because it's now optional.

---------

Co-authored-by: KN4CK3R <[email protected]>
    @merlleu @KN4CK3R @GiteaBot
    2 people authored and GiteaBot committed Oct 24, 2023
    Configuration menu
    Copy the full SHA
    f17f83e View commit details
    Browse the repository at this point in the history