[Bug]: __beta__ not respected if used in bundle layout in a .pulldown

[ING-MOP]

✈ Pre-Flight checks

• I don't have SentinelOne antivirus installed (see above for the solution)
• I have searched in the issues (open and closed) but couldn't find a similar issue
• I have searched in the pyRevit Forum for similar issues
• I already followed the installation troubleshooting guide thoroughly
• I am using the latest pyRevit Version

🐞 Describe the bug

beta = True works as intended when put in a script thats located in a panel without a bundle layout for me.
But if i make a bundle.yaml and add a Layout to tell the order of the scripts, it is not respecting the beta script to be invisible for non beta testers.

I havent tested if its still an issue outside of pulldowns

⌨ Error/Debug Message

No errors.

♻️ To Reproduce

No response

⏲️ Expected behavior

No response

🖥️ Hardware and Software Setup (please complete the following information)

==> Registered Clones (full git repos)
==> Registered Clones (deployed from archive/image)
master | Branch: "master" | Version: "6.4.0.26100+0515" | Path: "C:\Users\mop\AppData\Roaming\pyRevit-Master"
==> Attachments
master | Product: "2026 First Customer Ship" | Engine: DEFAULT (2712) | Path: "C:\Users\mop\AppData\Roaming\pyRevit-Master"
master | Product: "2025 First Customer Ship" | Engine: DEFAULT (2712) | Path: "C:\Users\mop\AppData\Roaming\pyRevit-Master"
master | Product: "2024.3" | Engine: DEFAULT (2712) | Path: "C:\Users\mop\AppData\Roaming\pyRevit-Master"
master | Product: "2023.1.4" | Engine: DEFAULT (2712) | Path: "C:\Users\mop\AppData\Roaming\pyRevit-Master"
master | Product: "2022.1.7" | Engine: DEFAULT (2712) | Path: "C:\Users\mop\AppData\Roaming\pyRevit-Master"
master | Product: "2021.1.9" | Engine: DEFAULT (2712) | Path: "C:\Users\mop\AppData\Roaming\pyRevit-Master"
==> Default Extension Search Path
C:\Users\mop\AppData\Roaming\pyRevit\Extensions
==> Extension Search Paths
K:\CAD\Revit\Revit Common\05_Development\MOP\GitHub Fake Server
C:\Users\mop\Github Local
==> Extension Sources - Default
https://github.com/pyrevitlabs/pyRevit/raw/master/extensions/extensions.json
==> Extension Sources - Additional
==> Installed Revits
2026 First Customer Ship | Version: 26.0.4.409 | Build: 20250227_1515(x64) | Language: 1033 | Path: "C:\Program Files\Autodesk\Revit 2026\"
2025 First Customer Ship | Version: 25.0.2.419 | Build: 20240307_1300(x64) | Language: 1033 | Path: "C:\Program Files\Autodesk\Revit 2025\"
2024.3 | Version: 24.3.0.13 | Build: 20240912_1515(x64) | Language: 1033 | Path: "C:\Program Files\Autodesk\Revit 2024\"
2023.1.4 | Version: 23.1.40.56 | Build: 20240411_0945(x64) | Language: 1033 | Path: "C:\Program Files\Autodesk\Revit 2023\"
2022.1.7 | Version: 22.1.70.9 | Build: 20240704_1515(x64) | Language: 1033 | Path: "C:\Program Files\Autodesk\Revit 2022\"
2021.1.9 | Version: 21.1.90.15 | Build: 20230907_1515(x64) | Language: 1033 | Path: "C:\Program Files\Autodesk\Revit 2021\"
==> Running Revit Instances
PID: 29636 | 2024.3 | Version: 24.3.0.13 | Build: 20240912_1515(x64) | Language: 0 | Path: "C:\Program Files\Autodesk\Revit 2024"
==> User Environment
Microsoft Windows 10 [Version 10.0.26200]
Executing User: INTERN\mop
Active User: INTERN\mop
Admin Access: No
%APPDATA%: "C:\Users\mop\AppData\Roaming"
Latest Installed .Net Framework: 10.0.4
Installed .Net Target Packs: v4.0 v4.5 v4.5.1 v4.5.2 v4.6 v4.6.1 v4.7.2 v4.8 v4.X
Installed .Net-Core Target Packs: v9.0.306
Active CPython Engine Version: 3123
pyRevit CLI v6.4.0.26100+0515.06e6e8108e8aaccfbb7080163a437e19236a8533

Additional context

[Wurschdhaud]

Can you try turning of the new launcher in settings and check if the issue persists?
If so, it should be linked to

• [Task]: New C# Loader Testing #2995

[Wurschdhaud]

Also as mentioned here stick to bundle files.

Metadata variables at the beginning of the script are deprecated in favour of bundle.yaml files - this is not an issue per se, but the problem arises when one uses both of them for the same script. To be on the safe, future-proof, side, just use bundle.yaml!

Plan is to drop support in favor of loading times and less stuff to maintain as per #3272