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.
This version was pushed to npm by pi0, a new releaser for nuxt since your current version.
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
You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/zurb/zurb-template/network/alerts).
Bumps loader-utils to 1.4.1 and updates ancestor dependency nuxt. These dependencies need to be updated together.
Updates
loader-utils
from 1.1.0 to 1.4.1Release notes
Sourced from loader-utils's releases.
... (truncated)
Changelog
Sourced from loader-utils's changelog.
... (truncated)
Commits
8f082b3
chore(release): 1.4.14504e34
fix: security problem (#220)d95b8b5
chore(release): 1.4.0cd0e428
feat: theresourceQuery
is passed to theinterpolateName
method (#163)06d36cf
chore(release): 1.3.0469eeba
feat: support the[query]
template for theinterpolatedName
method (#162)909c99d
chore: funding.yml config and CI fix (#159)b5b74f0
Set up CI with Azure Pipelines7970c48
docs: small grammar change (#144)b91a76c
chore(release): 1.2.3Maintainer changes
This version was pushed to npm by evilebottnawi, a new releaser for loader-utils since your current version.
Updates
nuxt
from 1.4.0 to 2.15.8Release notes
Sourced from nuxt's releases.
... (truncated)
Changelog
Sourced from nuxt's changelog.
Commits
d4b9e4b
v2.15.8af1d3e9
chore: skip audit due to outdated lockfile1ccd151
fix(vue-app): don't normalise route path if it's valid (#9460)af49199
fix(babel): loose option for babel private-property-in-object (#9631)4f370e2
v2.15.785615a5
fix(vue-app): check whether route exists within nuxt app before replacing (#9...0eae970
chore(release): v2.15.6fc5fb58
hotfix: revert feat additionscd1fc62
chore(deps): update ufo to 0.7.4a80ddee
chore(deps): update all non-major dependencies (#9281)Maintainer changes
This version was pushed to npm by pi0, a new releaser for nuxt since your current version.
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 You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/zurb/zurb-template/network/alerts).