Packages
igniter_new
0.5.32
0.5.34
0.5.33
0.5.32
0.5.31
0.5.30
0.5.29
0.5.28
0.5.27
0.5.26
0.5.25
0.5.24
0.5.23
0.5.22
0.5.21
0.5.20
0.5.19
0.5.18
0.5.17
0.5.16
0.5.15
0.5.14
0.5.13
0.5.12
0.5.11
0.5.10
0.5.9
0.5.8
0.5.7
0.5.6
0.5.5
0.5.4
0.5.3
0.5.2
0.5.1
0.5.0
0.4.12
0.4.11
0.4.10
0.4.9
0.4.8
0.4.7
0.4.6
0.4.5
0.4.4
0.4.3
0.4.2
0.4.1
0.3.8
0.3.7
0.3.6
0.3.5
0.3.4
0.3.3
0.3.2
0.3.1
0.3.0
0.2.4
0.2.3
0.2.2
0.2.1
0.2.0
0.1.0
Create a new mix project with igniter, and run igniter installers in one command!
Current section
Files
Jump to
Current section
Files
priv/docs/igniter.upgrade/long.txt
Fetch and upgrade dependencies. A drop in replacement for `mix deps.update`
that also runs upgrade tasks.
Updates dependencies via `mix deps.update` and then runs any upgrade tasks for
any changed dependencies.
By default, this task updates to the latest versions allowed by the `mix.exs`
file, just like `mix deps.update`.
To upgrade a package to a specific version, you can specify the version after
the package name, separated by an `@` symbol. This allows upgrading beyond what
your mix.exs file currently specifies, i.e if you have `~> 1.0` in your mix.exs
file, you can use `mix igniter.upgrade package@2.0` to upgrade to version 2.0,
which will update your `mix.exs` and run any equivalent upgraders.
## Limitations
The new version of the package must be "compile compatible" with your existing
code. See the upgrades guide for more.
## Example
mix igniter.upgrade package1 package2@1.2.1
## Options
* `--yes` - Accept all changes automatically
* `--all` - Upgrades all dependencies
* `--only` - only fetches dependencies for given environment
* `--verbose` - display additional output from various operations
* `--target` - only fetches dependencies for given target
* `--no-archives-check` - does not check archives before fetching deps
* `--git-ci` - Uses git history (HEAD~1) to check the previous versions
in the lock file. See the upgrade guides for more. Sets --yes
automatically.