github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-15 20:09:18 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Composer package registry "dev-main"/"dev-master" package version #9432

New Issue
Open
opened 2025-11-02 08:38:36 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 08:38:36 -06:00
Owner
Copy Link

Originally created by @faulkj on GitHub (Aug 20, 2022).

Feature Description

The built-in Composer package registry needs the automatically generated "dev-main"/"dev-master" version that points to the current main/master/[whatever we choose to call it] branch of a repository like we get on Packagist:

2022-08-19_21-01-38

Screenshots

No response

Originally created by @faulkj on GitHub (Aug 20, 2022). ### Feature Description The built-in Composer package registry needs the automatically generated "dev-main"/"dev-master" version that points to the current main/master/[whatever we choose to call it] branch of a repository like we get on Packagist: ![2022-08-19_21-01-38](https://user-images.githubusercontent.com/3419720/185728398-c9db81cd-60e2-454a-b5b9-ca978a3ef24f.png) ### Screenshots _No response_
GiteaMirror added the topic/packagestype/proposaltype/feature labels 2025-11-02 08:38:36 -06:00
GiteaMirror commented 2025-11-02 08:38:36 -06:00
Author
Owner
Copy Link

@KN4CK3R commented on GitHub (Aug 20, 2022):

The packages in the registry don't have a link to a repository. They are just uploaded archives with the source code.

@KN4CK3R commented on GitHub (Aug 20, 2022): The packages in the registry don't have a link to a repository. They are just uploaded archives with the source code.
GiteaMirror commented 2025-11-02 08:38:37 -06:00
Author
Owner
Copy Link

@morvy commented on GitHub (Jan 16, 2024):

A bit older question, but is this not supported yet? I have a package that I version with semver and that works fine, if I don't push tag, it fallbacks to version=dev-main, but putting the package to composer?version=dev-main or even "dev" will fail with error {"status":400,"message":"package version is invalid"}

@morvy commented on GitHub (Jan 16, 2024): A bit older question, but is this not supported yet? I have a package that I version with semver and that works fine, if I don't push tag, it fallbacks to version=dev-main, but putting the package to composer?version=dev-main or even "dev" will fail with error `{"status":400,"message":"package version is invalid"}`
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label topic/packages type/feature type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#9432
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?