Eldev 1.1.2

This release improves usability of option -W (--warnings-as-errors) to command compile and related. Previously they would fail after the very first warning (this is the standard behavior of Emacs byte-compiler, see byte-compile-error-on-warn). Now they abort compilation only after a .el file has been fully processed, thus showing all warnings (elevated to errors) in it. This is more similar to e.g. GCC behavior.

Eldev 1.1.1

This release fixes a couple of Windows-specific bugs in Eldev bootstrapping (Emacs 26) and installation in GitHub workflows.

As a minor improvement, command-line options that accept a number now issue a proper error when their argument cannot be parsed. Previously it would be possible to accidentally supply a different option as an optional argument to the previous one, only for it to silently get ignored by Eldev, e.g.: eldev test -sB.

Eldev 1.1

New in this release:

• GNU ELPA and NonGNU ELPA now have stable and unstable variants, just as MELPA. Previously existing archives have kept their names; combined archives are called gnu-elpa and nongnu-elpa, while the new unstable variants are gnu-devel (https://elpa.gnu.org/devel/) and nongnu-devel (https://elpa.nongnu.org/devel/). This should result in no changes for existing projects. It is recommended to change calls like (eldev-use-package-archive 'gnu) to (eldev-use-package-archive 'gnu-elpa), after which you can use standard options --stable/--unstable to switch between real releases and development snapshots if wanted.
• Forms for commands eval and exec now have access to “magic” variables called @, @1, @2... that allow you to easily refer to previous results.
• Command archives now has option --list-known (-L) that shows “standard” package archives that Eldev knows about and whether the current project uses them.

Eldev 1.0

This release mostly symbolizes that Eldev has reached feature-full state. But of course it doesn't mean development stops here.

Minor news:

• In non-debug (default) mode Eldev gives even more hints when an error happens. For example, when loading an Elisp file fails, it will print the name of the file. In debug mode you can see the full backtrace, as before.
• Fixes for Emacs 29 support (i.e. its master branch).

Eldev 0.11

New in this release:

• Profiling support provides a quick way to profile your project’s code. However, mainly due to Emacs limitations, homegrown solutions might be more convenient because of shorter backtraces.
• Several improvements for eval and exec commands, some generally useful, some targeted at the new profiling functionality.
• Global (i.e. non-project) Eldev files are now layed out according to XDG specifications. Existing installations are not affected, though.

Eldev 0.10.3

This release fixes a bug in functionality added in 0.10.2 in certain cases and also adjust tests accordingly.

Eldev 0.10.2

This release fixes a minor bug in ERT test result saving/restoring code. It also adds a minor feature: variables eldev-test-ert-fileset, eldev-test-buttercup-fileset etc. for multiframework support new in 0.10, see documentation.

Eldev 0.10.1

This release fixes two bugs in the support for multiple testing frameworks per project, added in 0.10.

Eldev 0.10

This release comes with several new features:

• Docker support lets you run Eldev commands easily. You can use both “standard” Silex’s Emacs images and your own.
• Partial support for Ecukes tests; only “script” (a.k.a. “batch”) mode is supported.
• You can now use several testing frameworks at once in the same project. This is needed by some larger projects.

Less important changes:

• Updated package-lint integration: Eldev will now set package-lint-main-file correctly for you.
• Yet more backtrace formatting improvements. In particular, backtrace formatting is now more similar across different Emacs versions.
• Several fixes.

Eldev 0.9.3

This release adds a workaround for certain bug that happens when installing newer Org from GNU ELPA on older Emacs versions. I don't know exactly what causes the bug precisely, but apparently force-closing HTTP(S) connections before installing next dependency “solves” it.

Note: currently Eldev self-tests fail, but only on Windows. This will be investigated separately.