Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 36,993
    • Issues 36,993
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1,450
    • Merge requests 1,450
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #240887

Closed
Open
Created Aug 24, 2020 by Gounlaf@Gounlaf

Packages/composer: semver not fully supported

Summary

Semver is not fully supported with the composer registry: metadata are not supported.

Steps to reproduce

  • Create a tag: v1.0.1+some-metadata

  • Add it to the registry via curl; + must be encoded, so I use json instead (curl -d '{"tag":"v1.0.1+metadata"}' -H 'Content-Type: application/json')

  • The package is reference as "1.0.1" instead of "1.0.1+some-metadata"

Pre-release works well (for example: 2.0.0-alpha.5)

Example Project

https://gitlab.com/Gounlaf/issue-composer-registry

What is the current bug behavior?

The metadata is stripped from the tag.

What is the expected correct behavior?

Metadata should be included in the

Relevant logs and/or screenshots

The API returns {"message":"201 Created"} in all cases

Output of checks

This bug happens on GitLab.com

Possible fixes

NOOP

I've search for bugs with label=~"Category:Package Registry" + label~"bug" + composer. I found no related issues.

Regards.

Assignee
Assign to
13.6
Milestone
13.6 (Past due)
Assign milestone
Time tracking