Skip to content

chore: use caret for some deps #2950

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

Merged
merged 1 commit into from
Jan 11, 2021
Merged

chore: use caret for some deps #2950

merged 1 commit into from
Jan 11, 2021

Conversation

alexander-akait
Copy link
Member

  • This is a bugfix
  • This is a feature
  • This is a code refactor
  • This is a test update
  • This is a docs update
  • This is a metadata update

For Bugs and Features; did you add new tests?

No need

Motivation / Use-Case

Use caret to avoid unnecessary releases, we still need bundle client, but now it will be avoid problems with server

Breaking Changes

No

Additional Info

No

@codecov
Copy link

codecov bot commented Dec 28, 2020

Codecov Report

Merging #2950 (6f2aee4) into master (ca9e45d) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #2950   +/-   ##
=======================================
  Coverage   92.54%   92.54%           
=======================================
  Files          37       37           
  Lines        1261     1261           
  Branches      334      334           
=======================================
  Hits         1167     1167           
  Misses         89       89           
  Partials        5        5           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ca9e45d...6f2aee4. Read the comment docs.

@alexander-akait alexander-akait merged commit 5029dd6 into master Jan 11, 2021
@alexander-akait alexander-akait deleted the deps-use-caret branch January 11, 2021 11:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants