-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Add enforce lockfile bootstrap command config #600
Conversation
…eLockfile property
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm!
@Ayman-Barghout the analyzer warnings are already fixed in #602, no harm in fixing them in here too to show that it is green though, as long as the other one is merged first. :) |
Oh, my bad, didn't notice :) sure thing, I am gonna wait till #602 merge then 🙌 |
Could we add this as a flag to bootstrap too, |
@Ayman-Barghout did you see Salakar's comment? |
Sadly not, just noticed it when you pinged 🙂 will work on it ASAP |
@Ayman-Barghout you can have a look at #604 to see how to do it :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One final comment, the rest looks good!
Co-authored-by: Lukas Klingsbo <[email protected]>
Co-authored-by: Lukas Klingsbo <[email protected]>
Co-authored-by: Lukas Klingsbo <[email protected]>
Co-authored-by: Lukas Klingsbo <[email protected]>
Co-authored-by: Lukas Klingsbo <[email protected]>
Co-authored-by: Lukas Klingsbo <[email protected]>
Co-authored-by: Lukas Klingsbo <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your contribution :)
* Enforce lockfile for CI environments * Add enforce lockfile to bootstrap command config * Enforce lockfile based on the bootstrap command workspace config * Update overview.mdx with enforce lockfile option * Update the `docstring` for `enforceLockfile` to include it is default for CI * Update workspace config and bootstrap tests to include the new enforceLockfile property * Stop enforcing lock file on CI by default * Remove unnecessary parenthesis as linter is complaining * Update enforcing lock files to be inclusive of Dart as well as Flutter Co-authored-by: Lukas Klingsbo <[email protected]> * Add `--enforce-lockfile` as a bootstrap flag * Fix duplicate calling of enforce lockfile flag * Consolidate bootstrap flags documentation * Update docs/commands/bootstrap.mdx for clarity Co-authored-by: Lukas Klingsbo <[email protected]> * Update docs/commands/bootstrap.mdx for clarity Co-authored-by: Lukas Klingsbo <[email protected]> * Update docs/commands/bootstrap.mdx for clarity Co-authored-by: Lukas Klingsbo <[email protected]> * Update docs/commands/bootstrap.mdx for clarity Co-authored-by: Lukas Klingsbo <[email protected]> * Update docs/commands/bootstrap.mdx formatting Co-authored-by: Lukas Klingsbo <[email protected]> * Update docs/configuration/overview.mdx for better clarity Co-authored-by: Lukas Klingsbo <[email protected]> * Update docs/configuration/overview.mdx for better clarity Co-authored-by: Lukas Klingsbo <[email protected]> --------- Co-authored-by: Lukas Klingsbo <[email protected]>
* Enforce lockfile for CI environments * Add enforce lockfile to bootstrap command config * Enforce lockfile based on the bootstrap command workspace config * Update overview.mdx with enforce lockfile option * Update the `docstring` for `enforceLockfile` to include it is default for CI * Update workspace config and bootstrap tests to include the new enforceLockfile property * Stop enforcing lock file on CI by default * Remove unnecessary parenthesis as linter is complaining * Update enforcing lock files to be inclusive of Dart as well as Flutter Co-authored-by: Lukas Klingsbo <[email protected]> * Add `--enforce-lockfile` as a bootstrap flag * Fix duplicate calling of enforce lockfile flag * Consolidate bootstrap flags documentation * Update docs/commands/bootstrap.mdx for clarity Co-authored-by: Lukas Klingsbo <[email protected]> * Update docs/commands/bootstrap.mdx for clarity Co-authored-by: Lukas Klingsbo <[email protected]> * Update docs/commands/bootstrap.mdx for clarity Co-authored-by: Lukas Klingsbo <[email protected]> * Update docs/commands/bootstrap.mdx for clarity Co-authored-by: Lukas Klingsbo <[email protected]> * Update docs/commands/bootstrap.mdx formatting Co-authored-by: Lukas Klingsbo <[email protected]> * Update docs/configuration/overview.mdx for better clarity Co-authored-by: Lukas Klingsbo <[email protected]> * Update docs/configuration/overview.mdx for better clarity Co-authored-by: Lukas Klingsbo <[email protected]> --------- Co-authored-by: Lukas Klingsbo <[email protected]>
Description
This change is to ensure which versions are being used, as minor changes sadly can have breaking changes to your codebase (conflicting names for example), so this option is to make sure all machines/environments are running the same versions.
This resolves #575.
Edit: Enforcing it on CI isn't a good idea as some monorepos don't check in lock files for packages if they are published, so it should always be optional.
Type of Change
feat
-- New feature (non-breaking change which adds functionality)fix
-- Bug fix (non-breaking change which fixes an issue)!
-- Breaking change (fix or feature that would cause existing functionality to change)refactor
-- Code refactorci
-- Build configuration changedocs
-- Documentationchore
-- Chore