greenkeeper[bot]
commented
4 years ago After pinning to 4.1.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Open greenkeeper[bot] opened 4 years ago
greenkeeper[bot]
commented
4 years ago After pinning to 4.1.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
greenkeeper[bot]
commented
4 years ago devDependency @vue/cli-plugin-babel was updated from 4.1.1 to 4.1.2.Your tests are still failing with this version. Compare changes
The new version differs by 20 commits.
3b7227d v4.1.295ae2a1 chore: merge branch 'master' into dev0cba512 fix: fix several bugs in the PWA plugin UI, make it usable again (#4974)1594327 chore: fix link to himepage (#5004)9e73907 docs: update example code (#4987)ef548a7 Update debugging instructions (#4754)7bc3cd7 docs: his -> their (#4976)3f15b4c mention navigateFallback in the pwa docs (#4973)00acca5 refactor: use inline approach (#4904)26bdb51 fix: typo errors (#4938)f7b95ac fix: should download to different directories for different pre… (#4922)02f2436 docs: [RU] Translation update (#4917)c7961cd fix: do not throw when babel config contains ignore/include/exclude (#4924)aeddc6f refactor: changed var async to isAsync (#4909)6c24964 chore: remove unused dependency "slash"There are 20 commits in total.
See the full diff
greenkeeper[bot]
commented
4 years ago devDependency @vue/cli-plugin-babel was updated from 4.1.2 to 4.2.0.Your tests are still failing with this version. Compare changes
First, reinstall the latest version of @vue/cli globally.
yarn global add @vue/cli
# OR
npm install -g @vue/cli
Then in the projects, run
vue upgrade
A critically CORS vulnerability is fixed in this version.
We recommend all users of vue ui to upgrade to this version as soon as possible.
From this version on, newly-created projects and newly-added CLI plugins will lock the plugin version ranges to their minor versions.
The core functionalities of Vue CLI is quite stable at the moment.
We made this change to improve project stability even more.
Users can run vue upgrade periodically to bump the minor versions in the projects.
We also expect this change to make the adoption of new features smoother.
See more detailed explanation at #5012
With the recent updates in the ecosystem (eslint-plugin-vue, @vue/eslint-config-airbnb, @vue/eslint-config-standard, @vue/eslint-config-prettier, @vue/eslint-config-typescript), Vue CLI now supports ESLint 6. It will scaffold all new projects will ESLint 6.
For users from older versions, ESLint 5 is still supported. If you want to adopt ESLint 6 in the project, it's recommended to migrate through the vue upgrade command; otherwise, there will be much manual work to do.
We now support the optional chaining and nullish coalescing operators!
// Optional chaining
a?.(); // undefined if `a` is null/undefined
b?.c; // undefined if `b` is null/undefined
// Nullish coalescing
undefined ?? 'some other default'; // result: 'some other default'
null ?? 'some other default'; // result: 'some other default'
'' ?? 'some other default'; // result: ''
0 ?? 300; // result: 0
false ?? true; // result: falseIf you're using Babel, these syntaxes supported by default since this version, so no actions to take.
If you're using TypeScript, the vue upgrade command will automatically do the necessary
configurations for you, or you can manually upgrade your typescript dependency to 3.7.0 or later.
vue upgrade and vue migrateSee the Pull Request at #5091
You may have encountered the TypeError: Invalid Version: N/A error if you ran vue upgrade in a monorepo or forgot to run npm install first.
It is because, to run corresponding migration scripts, Vue CLI needs to know which versions of plugins the project previously depended on.
Monorepo support has been added since v4.2.
But in case of missing dependencies or any other edge cases, you can pass a --from option to the command to skip the local version detection step. For example: vue upgrade eslint --from 4.1.2.
A vue migrate --from command is available for those already bumped to the latest versions but didn't run the migration scripts.
vue upgrade.~3.5.3 to ~3.7.5. Users can upgrade through vue upgrade, or manually change the dependency version in package.jsontests/e2e/.eslintrc. We haven't implemented an automatic migration script for it. Please add it manually. See https://github.com/vuejs/vue-cli/blob/v4.2.0/packages/%40vue/cli-plugin-e2e-nightwatch/generator/template/tests/e2e/_eslintrc.js#L5@vue/test-utils version used for unit tests is bumped from 1.0.0-beta.29 to 1.0.0-beta.31. Due to the breaking changes, we didn't migrate it automatically for old projects. Please read the release notes and upgrade at your own will.@vue/cli-plugin-babel, @vue/cli-plugin-eslint, @vue/cli-plugin-typescript, @vue/cli
@vue/cli-plugin-unit-jest, @vue/cli-plugin-unit-mocha
@vue/cli-ui, @vue/cli
@vue/cli-plugin-typescript, @vue/cli-ui
@vue/cli
@vue/cli-service
--stdin flag to serve (@nullpilot)@vue/babel-preset-app, @vue/cli-plugin-e2e-nightwatch, @vue/cli-plugin-eslint, @vue/cli-plugin-pwa, @vue/cli-ui-addon-webpack, @vue/cli-ui-addon-widgets, @vue/cli-ui, @vue/cli
@vue/cli-service, @vue/cli-shared-utils, @vue/cli
@vue/babel-preset-app
@vue/cli-service-global
@vue/cli-shared-utils, @vue/cli
@vue/cli
afterInvoke/onCreateComplete callbacks in Migrator (@sodatea)extendPackage dependency versions should be string (@pksunkara)@vue/cli-ui, @vue/cli
@vue/cli-plugin-e2e-cypress
--headless work with --browser chrome (@LinusBorg)@vue/cli-service
@vue/cli-plugin-pwa
@vue/cli-plugin-unit-jest, @vue/cli-plugin-unit-mocha
@vue/cli-service, @vue/cli-test-utils
@vue/cli-plugin-e2e-nightwatch
@vue/babel-preset-app, @vue/cli-plugin-babel
@vue/cli-service
@vue/cli
@vue/cli-shared-utils
@vue/cli-plugin-router, @vue/cli-plugin-typescript, @vue/cli-service
The new version differs by 69 commits.
079a451 v4.2.0d493491 chore: pre release sync6d680bc fix(migrator): correctly extract config fields to files246c197 fix: clear require cache after upgrade, before migrateef15316 fix: preserve the tilde version range after vue upgrade51a4da7 fix: should infer package manager from config if there's no lockfile in the project (#5150)f5f4de0 feat(GeneratorAPI): allow passing options to api.extendPackage (#5149)9a1d52e feat: create projects with @vue/test-utils beta 31 (#5147)adef4c9 fix(e2e-nightwatch): fix eslint config generation (#5148)c5bf5b1 chore: update chromedriver version to 80e6d7bbd feat: implement a migrator that updates the project's ts version82bd074 refactor: use dep versions from plugin package.json1b64ff8 fix: fix eslint errors for typescript + e2e-nightwatch setupe4410b8 fixup! fix: fix duplicate slash in metadata url813680e fix: should use the local version number if the cache falls behindThere are 69 commits in total.
See the full diff
greenkeeper[bot]
commented
4 years ago devDependency @vue/cli-plugin-babel was updated from 4.2.0 to 4.2.1.Your tests are still failing with this version. Compare changes
The new version differs by 17 commits.
8b951f8 v4.2.1776275d fix: add graphql-server.js to npm filesd7acff5 chore: merge branch 'dev' into master807382c chore: refine changelog [ci skip]7f2140a docs(en): update polyfill import according to core-js 3 docs (#5130)9f0b1f6 fix(docs): new travis CLI interface (#5126)9e18f3c Add a demo for multiple loader (#5122)771182e docs(zh): update polyfill import according to core-js 3 docsff8f035 docs: [RU] Translation update (#5094)5edafc0 line 477 according to english version (#5081)b5dedc1 Add a demo for multiple loaders (#5076)cf5f009 Mention that Vue CLI should be installed in Prototyping guide (#5079)1790205 fix: fix a typo (#5078)49f70ba docs: mention the precedence of .vue & .ts(x) extensions (#5055)e8fb3d9 docs(zh): Sync Chinese translation (#5051) [ci skip]There are 17 commits in total.
See the full diff
greenkeeper[bot]
commented
4 years ago devDependency @vue/cli-plugin-babel was updated from 4.2.1 to 4.2.2.Your tests are still failing with this version. Compare changes
greenkeeper[bot]
commented
4 years ago devDependency @vue/cli-plugin-babel was updated from 4.2.2 to 4.2.3.Your tests are still failing with this version. Compare changes
@vue/cli
@vue/cli-service-global
@vue/cli
The new version differs by 18 commits.
0380f22 v4.2.3a6c35cd chore: merge branch 'dev'da84840 docs: add page title & fix link [ci skip]d8db292 fix: fix "Vue packages version mismatch" error caused by other global packages (#5163)5cb988c fix(GeneratorAPI): remove warning when using extendPackage with prune (#5202)69f6805 fix(cli-service-global): fix no-debugger rule config (#5196)7225649 docs: vue-cli -> Vue CLI33487a8 workflow: allow manually specifying dist-tag when releasingc39eb72 docs(zh): fix typo in mode-and-env.md (#5224)bd12771 Remove unnecessary hyphen (#5184)480ac7f chore: minor typographical fix (#5215)b08c10f docs(zh): update example format (#5209)efbc20c docs(zh): Update now 404 url (#5141)1423553 chore: Minor typographical fix (#5189)677e4c5 Added basic upgrading instructions (#5176)There are 18 commits in total.
See the full diff
The devDependency @vue/cli-plugin-babel was updated from
4.1.0to4.1.1.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
@vue/cli-plugin-babel is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/maxpou/dictionary-game/builds/617779078?utm_source=github_status&utm_medium=notification)).Release Notes for v4.1.1
@vue/cli-plugin-typescriptCommitters: 1
Commits
The new version differs by 3 commits.
2ddcc65v4.1.1dd98fa6fix: fix tsx compilation (#4894)d21245dworkflow: correctly decide which dist-tag to useSee the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: