I’m using branches for some components that I sourced using the Advanced Install modal. A recent update on instances hosted by CDCK reset all components to use the main branch. The source link referred to the main branch instead of ../tree/branch-name.
AI-generated summary
The discussion revolves around a recent update that reset component branches to the main branch on instances hosted by C DCK, affecting components like discourse-tag-banners and discourse-category-banners. manuel reports that their branches were replaced with the main branch despite no changes to the branches themselves, noting that the issue only occurred on C DCK-hosted sites, not self-hosted ones. sam responds that no recent changes were made to cause this, though some past changes were made months ago, and questions whether this is a regression or if the user returned to development after a long break. manuel provides additional context, confirming they updated the main branch and added a new branch but did not use it on production, and the issue seems isolated to C DCK-hosted instances.
1 Like
We had some internal chatter and are not aware of any changes we made that would have caused this in the past few weeks.
We did make some changes in this area a few months ago though… are you getting back to developing on your branches after a long hiatus? Do you think this is a recent regression?
2 Likes
Ok, I don’t know how I’d debug that in more detail. Just in case, sharing what seemed to happen in more detail:
- I use branches of the discourse-tag-banners and discourse-category-banners components (for use with the sidebar and with the layouts plugin)
- I didn’t change existing branches, but I
- updated the main branch of my forks
- and added a new branch to my forks. I’m not using this branch on any production site though
- the already installed components used on sites hosted by CDCK switched to sourcing the main branch of my forks
- the branches on self-hosted sites did not change.