Can't publish new package versions anymore #11504

New Issue

GiteaMirror · 2025-11-02T09:39:34-06:00

GiteaMirror commented

2025-11-02 09:39:34 -06:00

Originally created by @trading-peter on GitHub (Aug 21, 2023).

Description

I was able to push packages without problem but since one of the last updates it stopped worked all the sudden.

My setup:

I have a organisation called "tp-elements"
I'm in the owner group of that organisation. Checked like 10 times at this point lol.
There are 32 repos in the org, each one als gets published as a NPM package by me.
I can pull packages using npm install without problems.
All packages are scoped in a "@tp" namespace.
NPM output is the following
Gitea logs show this if I try to push.

Gitea Version

1.20.3

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

Running it self-hosted using docker-compose.

Database

PostgreSQL

Originally created by @trading-peter on GitHub (Aug 21, 2023). ### Description I was able to push packages without problem but since one of the last updates it stopped worked all the sudden. My setup: - I have a organisation called "tp-elements" - I'm in the owner group of that organisation. Checked like 10 times at this point lol. - There are 32 repos in the org, each one als gets published as a NPM package by me. - I can pull packages using npm install without problems. - All packages are scoped in a "@tp" namespace. - NPM output is the following ![image](https://github.com/go-gitea/gitea/assets/11567985/1fdbbf16-b0eb-4990-9b52-c13422c37ae0) - Gitea logs show this if I try to push. ![image](https://github.com/go-gitea/gitea/assets/11567985/1fdbf0e9-000e-4220-aca9-275e6588fcf1) ### Gitea Version 1.20.3 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? Running it self-hosted using docker-compose. ### Database PostgreSQL

GiteaMirror added the issue/not-a-bug label 2025-11-02 09:39:34 -06:00

GiteaMirror closed this issue

2025-11-02 09:39:34 -06:00

GiteaMirror commented

2025-11-02 09:39:35 -06:00

@techknowlogick commented on GitHub (Aug 21, 2023):

Did you upgrade from 1.20.2 or some other version?

@techknowlogick commented on GitHub (Aug 21, 2023): Did you upgrade from 1.20.2 or some other version?

GiteaMirror commented

2025-11-02 09:39:35 -06:00

@trading-peter commented on GitHub (Aug 21, 2023):

I think I upgraded from 1.20.1 if I recall correctly

@trading-peter commented on GitHub (Aug 21, 2023): I think I upgraded from 1.20.1 if I recall correctly

GiteaMirror commented

2025-11-02 09:39:35 -06:00

@trading-peter commented on GitHub (Aug 22, 2023):

I figured it out.
Seems like there was a new setting added, or it got reset or whatever. Once I enabled the package registry on the repo that wanted to push a new npm package version it worked again.

@trading-peter commented on GitHub (Aug 22, 2023): I figured it out. Seems like there was a new setting added, or it got reset or whatever. Once I enabled the package registry on the repo that wanted to push a new npm package version it worked again. ![image](https://github.com/go-gitea/gitea/assets/11567985/8cc28333-0bb5-44b4-b606-a656e685a881)

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#11504