Dependency re-testing #15084

New Issue

GiteaMirror · 2025-11-02T11:29:48-06:00

GiteaMirror commented

2025-11-02 11:29:48 -06:00

Originally created by @bilogic on GitHub (Nov 1, 2025).

Feature Description

Let's say I have PHP composer 2 repos, A and B
B requires A to function (the dependency)
Thus, when I commit to A and all tests are passing, I would like B to re-test itself using the latest A

Possible?

Note: this is a simplified example, in reality, the dependency has to be parsed from the composer.json of each repo

I'm currently using the API to achieve this, but a built-in way would be wonderful

Screenshots

No response

Originally created by @bilogic on GitHub (Nov 1, 2025). ### Feature Description 1. Let's say I have PHP composer 2 repos, A and B 2. B requires A to function (the dependency) 3. Thus, when I commit to A and all tests are passing, I would like B to re-test itself using the latest A Possible? Note: this is a simplified example, in reality, the dependency has to be parsed from the `composer.json` of each repo I'm currently using the API to achieve this, but a built-in way would be wonderful ### Screenshots _No response_

GiteaMirror added the type/proposal label 2025-11-02 11:29:48 -06:00

GiteaMirror commented

2025-11-02 11:29:49 -06:00

@lunny commented on GitHub (Nov 1, 2025):

I don't think that should be triggered automatically because B should require A's some special commit/revision. Otherwise, it will become a disaster.

@lunny commented on GitHub (Nov 1, 2025): I don't think that should be triggered automatically because B should require A's some special commit/revision. Otherwise, it will become a disaster.

GiteaMirror commented

2025-11-02 11:29:49 -06:00

@bilogic commented on GitHub (Nov 2, 2025):

Yes,

B must specify in the composer.json which semantic versions it can accept
A must not make breaking changes according to semantic versioning
But in real world, mistakes are often made
So this re-testing is to catch these mistakes

@bilogic commented on GitHub (Nov 2, 2025): Yes, 1. B *must* specify in the `composer.json` which semantic versions it can accept 2. A *must* not make breaking changes according to semantic versioning 3. But in real world, mistakes are often made 4. So this re-testing is to catch these mistakes

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#15084