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
Description
It is convenient, but problematic, to pin SPM packages to branches. Branches changes, which mean that builds are not repeatable. Both DavidFoundation and LaunchAtLogin are currently pointing to main.
It's less-convene it, but far safer, to put specific commits in there. This way, you guarantee that you have controlled what going is going into what version, and that updates are intentional instead of a side-effect of building.
Type
Non-UI
Mockups
Optional Information
Additional Information
Checklist
I have filled out everything under Mandatory Information
The text was updated successfully, but these errors were encountered:
Oh, good eye! I never noticed they were pointing at a branch. Would it be okay to change them to "Up to Next Major Version", or do you think they should really be pointing to a specific commit?
I think Up to Next Major Version is the right choice if there actually is a release that will work. But, if you need something on a branch that hasn't been released, a specific commit is safest.
Feature Suggestion
Mandatory Information
Description
It is convenient, but problematic, to pin SPM packages to branches. Branches changes, which mean that builds are not repeatable. Both
DavidFoundation
andLaunchAtLogin
are currently pointing tomain
.It's less-convene it, but far safer, to put specific commits in there. This way, you guarantee that you have controlled what going is going into what version, and that updates are intentional instead of a side-effect of building.
Type
Non-UI
Mockups
Optional Information
Additional Information
Checklist
The text was updated successfully, but these errors were encountered: