How handle versioning in my npm repo package and update the repo - npm

Question

I have an npm package which we created to use within the company.
It has the following package.json:
{
"name": "#company/eslint-config-company-base",
"version": "1.0.4",
"description": "ESLint base configuration file",
"main": "index.js",
"private": false,
"repository": {
"type": "git",
"url": "git+https://github.com/company/eslint-config-company-base.git"
},
"keywords": [
"eslint",
"config",
"airbnb",
"typescript",
"prettier"
],
"author": "company",
"license": "MIT",
"bugs": {
"url": "https://github.com/company/eslint-config-company-base/issues"
},
"homepage": "https://github.com/company/eslint-config-company-base",
"dependencies": {
"#typescript-eslint/eslint-plugin": "^2.6.0",
"#typescript-eslint/parser": "^2.6.0",
"eslint": "^6.6.0",
"eslint-config-airbnb": "^18.0.1",
"eslint-config-airbnb-base": "14.0.0",
"eslint-config-prettier": "^4.3.0",
"eslint-plugin-import": "^2.18.2",
"eslint-plugin-jsx-a11y": "^6.2.3",
"eslint-plugin-prettier": "^3.1.1",
"eslint-plugin-react": "^7.16.0",
"eslint-plugin-react-hooks": "^2.2.0"
}
}
It's created 3 years ago. I have to update all the dependencies.
So the way to go is:
update all the packages
is it enough to change the version number "version": "1.0.4", in the package.json, so you can run npm i -D #company/eslint-config-company-base#latest
which version number should it be. Should it be 2.0.0? From the changelog of the packages I can read there are some breaking changes