Tags: rubyworks/qed

Remove dead qed.yml symlink and pin kramdown dependency.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

The RC gem is optional now and old school `etc/qed.rb`, `config/qed.r…

…b` and

`.qed` are all supported again.

IMPORTANT! The `.qed` configuration file is no longer used for config…

…uration. Either use a unified `Config.rb` file or require a special config file via the `-r` option, e.g. `qed -r ./config/cov.rb`.

Configuration is now handled by the RC library. The only other form of configuration supported is that of requiring a special file directly via `-r ./path/to/file.rb`. This keeps the code as simple as possible without giving-up functionality. Because the old `.qed` configuration file is no longer supported, this release has a major version bump.

Feel like a heel after the last four releases. The simplist solution

to the configuration issue is to allow traditional configuration
trump confection based configuration. If the former is used, then
the later will never even load. Problem solved.

Release fixes a bug that prevented default demo locations from being …

…used when none are specified on the command line. Also change way to deactivate use of Confection for configuration, use environment variable `config='legacy'`.

This release simply make the configuration more versitile by supporti…

…ng Confection, task directory and traditional `.qed` configuration.

Just a fix of a method that should have been renamed. Nothing to see …

…here.

What a difference a week makes ;) The Confection library has been sub…

…stantially improved and if that trend contiunes at all then I think it will be well worth supporting. So with this release QED will again move configuration handling over to Confection. Jump over to the Confection project to learn how to use it. In short, this release reverts the previous release. Along with this change, profiles are now specified via the `-p`/`--profile` command line option instead of specialized options.

This release fixes a bug in the parsing of `#=>` notation. It also

adds syntax highlighting to qedoc generated documentation. It does
this with highlight.js.

IMPORTANT: READ THIS RELEASE NOTICE! This release makes a minor

change, but it is one that will effect all end-users. That is, QED no
longer depends on AE as its one and only assertion framework. Instead
any compliant framework can be used. Certainly most users will be happy
to continue using AE, in which case simply add `require 'ae'` to your
applique (e.g. in 'spec/applique/ae.rb') or add `-r ae` to the qed command
line invocation to ensure demos continue running as before. In place of
AE the _BRASS_ gem now provides basic assertion support. Any assertion
framework that complies with the simple BRASS standards will work with QED.