Otherwise we only get silent failures. This has been fixed a while ago
in mainline rebar3 but never in the bootstrap script.

Support `profile_string` overlay var in releases

Reload logger config in CT suites

Fixes #2159; this is done by force-reloading the handlers to match the
config.
This can create a bit of a funny effect if sys.config specifies an INFO
log level (or lower) is specified. While apps are booted for config
changes before the cth_failonly hook is enabled, supervision and other
application log messages can start being output. They will start being
suppressed once the CT run begins.

This is not a bug, it's a race in instantiation of control and enabling
of log levels. Nothing we can do about that. It might however surprise
people a good bit. If non-default stdout handlers are added, they are
similarly likely to become noisy; specifying a test-specific sys.config
file may be necessary then.

Also includes a bump of cth_readable version, which now checks for
updates to the log formatter on every test output.

Disable the default logger handler in shell if required

Fix case clause which used wrong element order

See http://erlang.org/doc/man/ct_hooks.html#Module:on_tc_fail-4

To avoid a conflict the Kernel's default handler have to be disabled
before the new default handler is added

    {kernel,
     [{logger,
       [{handler, default, undefined}
       ]}
     ]},
    {my_app,
     [{logger,
       [{handler, default, my_handler, #{}}
       ]}
     ]}

To support this behavior in shell it's necessary to process the
handler-default-undefined tuple.

It's not clear what to do with the simple handler (logger_simple_h)
however.  It's added at the start and removed if a default handler was
added.  Should it be added in reread_logger_config/1 if there's no
default handler?

Fix a couple typos in readme

upgrade relx 3.33.0

format error from provider init and print as warning

support REBAR_BASE_DIR for setting the base_dir

Fixing duplicate macro definition in umbrella edoc

Update vendored in hex_core to version 0.5.1

When in umbrella mode (or through multiple profiles), users can specify
macros for EDocs based on either the {def, ...} or the {macros, ...}
arguments.

This patch replaces the prior options merging for umbrellas to use the
rebar3 tup_umerge utils to remove identical duplicates while preserving
correct ordering, and manually merges the {macros, ...} definitions
while ke eping the correct precedence rules since these appear (given
their behaviour) to be all individually extracted and passed as `{d,
...}` to  the compiler so that epp expands them. This compiler
function freaks out on any re-defined macros and explodes.

Do note that the macros with `{def, ...}` are edoc macros and do not
suffer from that issue, safely deduplicating multiple definitions.

version 0.5.1 is a maintenance release of hex_core specifically for
 rebar3 which contains a configuration update. Prior to v0.5.1 if no
 repo_organization key was set this could result in a function clause
 error. The behavior is to now set repo_organization to undefined in
 this case.

Repair edoc functionality on rebar3 itself

de-duplicate dependency list in rebar_compiler_erl.erl

Fix reloading logger_level

OTP kernel application use "logger_level" configuration for configuring
level in primary configuration.
rebar3 uses "logger_info" for this purpose - ths is little bit confusing
and probably mistake.
This commit will unify behavior between kernel and rebar3o

Fixes: 0303567d95 ("Reload logger config in shell")

rebar3 dialyzer: Warn when debug_info is disabled

keep resources in new state used in plugins upgrade

Fix crash when a dependency is missing app.src file

Fix custom compiler mods typespecs, add edoc

Ensure EDoc opts in umbrella apps are respected

Patch up and add tests on #2112

Bump cth_readable to fix lager on OTP-21+

This adds an additional loading and merging of options for EDoc using
the values from the top-level along with those specified in the
rebar.config of an umbrella application.

The app-specific config values are prepended to the global ones; this
can likely cause some problems with manual path handling, but is
unlikely to happen in practice and the rest seems to work fine based on
order

Fixes the issue in #2114