Skip to content
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

Bump nuxt from 1.4.1 to 2.15.6 in /app #291

Closed

Conversation

dependabot-preview[bot]
Copy link
Contributor

Bumps nuxt from 1.4.1 to 2.15.6.

Release notes

Sourced from nuxt's releases.

v2.15.6

🐛 Bug Fixes

  • types
    • #9270 Pin to @types/webpack-dev-middleware@4.1.2 (resolves #9268)

v2.15.5

🐛 Bug Fixes

  • babel
    • #9232 Loose option for babel class-properties and private-methods (resolves #9224)
  • vue-app
    • #9201 Use route.replace instead of router.push to trigger navigation guards (resolves #9111)
  • builder
    • #9153 Resolve aliases in build.watch paths (resolves #9045)
  • cli
    • #9152 Add warning for css-loader < 4.2 (resolves #9117)

💖 Thanks to

v2.15.4

🐛 Bug Fixes

  • vue-app
    • #8978 Reload page once after loading chunk error (resolves #3389)
    • #9008 Fallback to global nuxt instance of $root is not available (resolves #8995)
    • #9010 Use app.context.route to match components in server (resolves #9009)
    • #9024 Serialize redirect functions in routes (resolves #8979)
    • #9026 Re-call $fetch if data is missing in payload (resolves #9016)
    • #9050 Use app.context.route for resolving components (resolves #9049)
    • #9075 Move internal app runtime config to _app namespace (resolves #9074)
  • config
    • #9014 Set compileType to icss for css-loader v4
  • server
    • #9034 Avoid caching .js assets in development to fix HMR in safari (resolves #3828)
  • cli

👕 Types

  • #9078 Inline @types/terser-webpack-plugin
  • #9086 Use options from sass-loader rather than sass (resolves #9085)
  • #9053 Css-loader v4 type definitions
  • #9018 Don't require all csp policies as keys (resolves #9017)
  • #9059 Add stub entrypoint to allow node resolution of @nuxt/types (resolves #9030)

... (truncated)

Changelog

Sourced from nuxt's changelog.

Release Plan

Starting with version v2.4, Nuxt will adhere to a formalized release plan (as good as possible). Also, an end of life for older major versions is defined with this document.

Major versions (3.x -> 4.0)

Nuxt major releases are planned every 6 months. This depends on a few factors though:

  • If there are no breaking changes waiting for a release, no new major version will be published. Instead, another minor one will be released
  • In case of unexpected major updates of important dependencies like Vue, Webpack, and so on, major versions might be released earlier than planned

The goal is to provide a migration guide for each major version as well, as escape hatches, so existing code won't "just break".

Minor versions (2.1 -> 2.2)

The release cycle for Nuxt minor versions is roughly 4 weeks.

Three of the four weeks will be used for actual feature implementations while the last week will be used for testing, fixing bugs and thorough audits.

That also means a feature freeze for the next minor version after these three weeks. Features that aren't ready will be moved to the next cycle. "Waiting" for features (for a longer time) will be avoided as good as possible to keep releases lean, concise, predictable and digestible.

Patch releases (2.2.3 -> 2.2.4)

The last patch releases were mostly bundled fixes or single hotfixes. In the future, fixes will be released as soon as possible after the actual PR/commit so people won't have to switch to nuxt-edge for bugfixes. This should improve the stability of Nuxt.

Fixes can or will include:

  • Updates of dependencies (for various reasons, like a "faulty/buggy" dependency or an newer versions that works better with the Nuxt code)
  • Fixes for our code

Bugfixes for upcoming features won't be ported of course.

Edge Release Channel

After experimenting with nuxt-edge releases in the last time, the decision to do nightly releases for now instead of releasing a version after each commit was made.

End of Life

Starting with v2.4, every major Nuxt version will have an End of Life. Previous releases will receive security updates and bugfixes for one year and two weeks, counted from the first release on. As Nuxt majors are approximately released once every 6 months, this will allow developers to "skip one major version" without being stuck with a broken or unsecure Nuxt dependency. The EOL also applies to the documentation.

Commits
  • 0eae970 chore(release): v2.15.6
  • fc5fb58 hotfix: revert feat additions
  • cd1fc62 chore(deps): update ufo to 0.7.4
  • a80ddee chore(deps): update all non-major dependencies (#9281)
  • 57a3307 chore: ignore @types/webpack-dev-middleware updates (ref: #9270)
  • 6d1e217 chore(deps): update all non-major dependencies (#9258)
  • aaf38ee chore(types): pin @nuxt/types dependency versions
  • 2f05597 chore: ignore @types/webpack-bundle-analyzer updates
  • 2b1c685 fix(types): pin to @types/webpack-dev-middleware@4.1.2 (#9270)
  • 9de997f v2.15.5 [release]
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by pi0, a new releaser for nuxt since your current version.


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label May 13, 2021
@dependabot-preview
Copy link
Contributor Author

Superseded by #304.

@dependabot-preview dependabot-preview bot deleted the dependabot/npm_and_yarn/app/nuxt-2.15.6 branch June 15, 2021 06:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants