You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think this will require using main as the dev release branch and then having separate release line branches so we can apply the branch protection to each of them and have the npm publish token accessible securely. So we would need to land (and possibly revert or follow-up) changes for it to get a dev release. I'm not sure if we can deploy directly from PR branches securely. 🤔
Activity
Qard commentedon May 31, 2025
I think this will require using
main
as the dev release branch and then having separate release line branches so we can apply the branch protection to each of them and have the npm publish token accessible securely. So we would need to land (and possibly revert or follow-up) changes for it to get a dev release. I'm not sure if we can deploy directly from PR branches securely. 🤔mcollina commentedon May 31, 2025
We do this in platformatic/platformatic by whitelisting specific branch manually when needed. Or we could apply it with a wildcard "prerelease/*"