Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Pin dependencies #2027

Merged
merged 1 commit into from
Aug 25, 2022
Merged

Pin dependencies #2027

merged 1 commit into from
Aug 25, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 25, 2022

Mend Renovate

This PR contains the following updates:

Package Type Update Change
@types/flatpickr devDependencies pin ^3.1.2 -> 3.1.2
ts-jest devDependencies pin ^26.5.6 -> 26.5.6

Add the preset :preserveSemverRanges to your config if you don't want to pin your dependencies.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot requested a review from a team as a code owner August 25, 2022 19:19
@jasperfurniss
Copy link
Contributor

After reading through this whole doc and talking to others (@jasoncypret @thestephenmarshall )
I'm going to go with the renovate's official recommendation...
Pinning devDependencies & ranging our dependencies.
See this for more:
https://docs.renovatebot.com/dependency-pinning/#so-whats-best

@jasperfurniss jasperfurniss merged commit 9ca0aff into master Aug 25, 2022
@jasperfurniss jasperfurniss deleted the renovate/pin-dependencies branch August 25, 2022 21:53
@jasperfurniss jasperfurniss added improvement This is used when your PR contains library upgrades or doc/site improvements. (USED IN CHANGELOG)) Ready for Release merged to master, ready for a versioned released labels Aug 25, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
improvement This is used when your PR contains library upgrades or doc/site improvements. (USED IN CHANGELOG)) Ready for Release merged to master, ready for a versioned released
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant