Sorry, this is not an issue, just a question that I can't find any answer to anywhere else. And the "discussions" isn't enabled in this repo.
Does Flatpak automatically update the VLC plugins to new branches?
This came up when I was subscribing to RSS/Atom feeds to all my installed Flatpak software GitHub commits (e.g. MakeMKV: https://github.com/flathub/com.makemkv.MakeMKV/commits/master.atom). I first thought that the plugins (makemkv and the java menu) weren't updated for a few years because I was looking at the "master" branch. Then I noticed the newer branches.
The master branch not updating anymore is a problem if somebody wants to be notified of updates. Because if I subscribe to the RSS/Atom of the newest branch 3-21.08 (https://github.com/flathub/org.videolan.VLC.Plugin.makemkv/commits/branch/3-21.08.atom) and you create a newer branch, it obviously won't be shown on that branch. Subscribing to the page of all branches (or just active branches) isn't possible in GitHub.
So, back to the issue question, if Flatpak doesn't automatically update to a new branch, it's a big possibility that a user doesn't know that the plugin is outdated. Especially if there's no way to subscribe to see newer branches in GitHub.
If Flatpak does not update the plugins automatically to new branches, maybe you could add a new file to the master (e.g. updatenotification.txt) and then each time you create a new branch, you would update that file in the master with something like "Please update your plugins to new branch". That way people could subscribe at least to the master commits RSS/Atom feed. If you have a better idea, please do that instead.
Or (just remembered that I have another plugin), look at the repo of G'MIC Flatpak plugin for GIMP. I don't understand how that repo and all the branches are managed. If you look at the 2-3.36 branch there, the last commit is a "EOL 2-3.36" which updated the flathub.json file with: "This version of the plugin is deprecated. Install org.gimp.GIMP.Plugin.GMic//2-40". However, if one looks at all the branches there, there isn't a new "2-40" branch. All updates seem to currently go to the master branch instead. Still my installation of that plugin show that it is in a "2-40" branch but receives the commits made to the master branch:
G'MIC org.gimp.GIMP.Plugin.GMic 3.0.2 2-40 system
They do something differently and can use the master branch for all updates?
EDIT: Just looked at what Flatpak offers for the G'MIC plugin:
flatpak install gmic
Looking for matches…
Found similar ref(s) for ‘gmic’ in remote ‘flathub’ (system).
Use this remote? [Y/n]:
Similar refs found for ‘gmic’ in remote ‘flathub’ (system):
1) runtime/org.gimp.GIMP.Plugin.GMic/x86_64/2-3.36
2) runtime/org.gimp.GIMP.Plugin.GMic/x86_64/2-40
It shows the new 2-40 which can't be found as a branch on the GitHub repo.
But, it seems that the plugins won't update automatically to the newer branches. If this is really true, while I'm not an expert with flatpaks, it seems to be a big design flaw of flatpak.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent