Skip to content

build(deps): bump distillery from 1.5.2 to 2.0.0 - #35

Closed
dependabot-preview[bot] wants to merge 1 commit into
masterfrom
dependabot/hex/distillery-2.0.0
Closed

build(deps): bump distillery from 1.5.2 to 2.0.0#35
dependabot-preview[bot] wants to merge 1 commit into
masterfrom
dependabot/hex/distillery-2.0.0

Conversation

@dependabot-preview

Copy link
Copy Markdown

Bumps distillery from 1.5.2 to 2.0.0.

Changelog

Sourced from distillery's changelog.

[2.0.0] - Unreleased

This is a major release with a number of significant changes and some of which are breaking,
please read these notes carefully! There are a great many improvements and bug
fixes. Unfortunately the bug fixes are so numerous that I can't list them all
here, but if you are interested, the git history is clean, and should
provide a good overview of what has been addressed.

Added

  • The Mix.Releases.Config.Provider behavior and API. Referred to as
    "Config Providers" in more general terms, this provides a format and source
    agnostic way to configure your application at runtime. Providers are executed
    during boot/init, after all application code is loaded, but before any
    applications are started (with the exception of kernel, stdlib,
    compiler, and elixir, as these are required to provide basic standard
    library functionality to providers). They are executed in the order listed in
    your config, and should push their configuration into the application
    environment (e.g. via Application.put_env/3). It is expected that when
    running multiple providers, the last one to run "wins" in the case of
    conflicting configuration keys, so they should be ordered by their priority.
  • A Mix.Config config provider, supporting config.exs scripts in releases.
    You can find more information in the Mix.Releases.Config.Providers.Elixir
    module docs, or in the Distillery documentation about config providers.
  • A new config_providers setting for defining which config providers to
    execute in a release (can be set in either environment or release blocks).
  • Support for writing a PID file to disk (useful for running under systemd in
    particular). It is enabled with -kernel pidfile "path/to/pidfile" or by
    exporting PIDFILE in the environment. When enabled, the file is written to
    disk and then checked every 5s - if the file is deleted, the node is
    terminated as soon as the next check is performed. This process is executed as
    a kernel process, and so should survive :init.restart/0.
  • Provide release.gen.appup task, for generating .appup files for a given
    application and version. This can be used to generate appups under rel for
    safe keeping, and easy modification. See mix help release.gen.appup for more
    details, it is a huge improvement if you are using hot upgrades!
  • Provide "read-only" mode for management scripts, which do not write any files
    when RELEASE_READ_ONLY is exported in the environment. This is intended to
    be used for executing commands as a user other than the one used to start the
    release via foreground, start, or console,
  • Raise a friendlier error when the ERTS specified was compiled for another OS when
    booting the release
  • Provide appup transforms - a plugin system for modifying appups
    programmatically during release builds.

Fixed

  • A lot of bugs, too many to list here
... (truncated)
Commits
  • b2b2f0b Version 2.0.0
  • 39ee772 Fix foreground mode on Windows
  • b1c3525 Add additional Windows helpers, some tweaks to existing ones
  • 2fde266 Add warning about Windows gotcha in installation doc [ci skip]
  • f472343 Version 2.0.0-rc.12
  • 35ad523 Update windows scripts for 2.0
  • 0a311a1 Problem: upfrom option is not recognized (#481)
  • be6d5e9 Fix handling of RELEASES; support release selection
  • e2f48a8 Clean up erl() and erlexec(); make sure __set_code_paths() handles symlinked ...
  • e01d8d5 Ensure -config is set for erl when present
  • Additional commits viewable in compare view

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 merge will merge this PR after your CI passes on it
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major 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)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • 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)

Finally, you can contact us by mentioning @dependabot.

@dependabot-preview

Copy link
Copy Markdown
Author

Superseded by #36.

@dependabot-preview
dependabot-preview Bot deleted the dependabot/hex/distillery-2.0.0 branch August 16, 2018 06:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant