@catch submitted a patch and changed the version on #2652068-11: Update jcalderonzumba/gastonjs to a tagged release - the patch failed to apply because the DCI_CoreBranch was the old value of 8.0.x and not the new value of 8.1.x.

Comments

alexpott created an issue. See original summary.

drumm’s picture

Status: Active » Postponed

I'm tempted to close this as a duplicate of #1171958: Allow files to be assigned to branch(es)/version(s) and thus tested against it since that's also blocking #66484: Allow issues to be filed against multiple versions/branches..

A more-immediate solution would be figuring out where a static cache is being hit within pift_node_update(), and make sure that cache isn't hit. Or move the whole thing to somewhere after the node update process.

drumm’s picture

Title: DCI_CoreBranch is wrong if a patch is uploaded and the version is changed on the same comment » Update file's version for testing when issue's version is selected
Priority: Major » Normal
Status: Postponed » Active

With #1171958: Allow files to be assigned to branch(es)/version(s) and thus tested against it, files now get their own relationship to the branch for testing, regardless of the issue.

There is still a gap we can make nicer with some JS. When the issue's version is selected, the file's version should update too.

drumm’s picture

Category: Bug report » Task