A slight breaking change in this release: The "last modified" date is no longer being
used in the blog. Instead, the date shown is only the slug date, which makes the date
more accurate when pre-dating posts.
The last_modified
attribute is now simply called date
, which makes it a bit more
general-purpose. This means that you'll need to re-bundle your templates.
A change to Beam::Wire means a change to Statocles
config files: $method
in the event handlers is now $sub
, so if you have configured
the LinkCheck plugin, you'll get a deprecation warning from Beam::Wire.
The site creator now allows you to set the base_url
, since that's required for
Statocles to work properly. It also, if given a site as an argument, creates the
site's directory.
Full changelog below:
Continue reading Release v0.041...
The biggest new thing in this release is the new LinkCheck
plugin that checks all the pages for
broken links and images. This introduces a new event-handling API into
Statocles, which will be called Plugins. See the developer
docs for more information on plugins.
A bunch of bug fixes for the create
command. It now actually works, instead
of creating an unusable site.yml
file.
The default build directory is now .statocles/build
instead of .statocles-build
.
It is anticipated we might use the .statocles
directory for some additional
site metadata.
With Mojolicious 6.0 release, there were a few breaking
changes that we needed to fix in Statocles. We now require 6.0.
Full changelog below:
Continue reading Release v0.040...
This is it! The beta milestone is complete!
This release adds the "create" command to easily create new Statocles sites.
Blog posts are now directories, which will allow us (in the future) to have
images and other documents inside. The breaking part of this change was made now,
and future additions will be made as beta progresses.
There were a couple reorganizations of the documentation and tests to make them
easier to understand.
Full changelog below:
Continue reading Statocles Beta (Release v0.039)...
With a new way to quickly build old git versions, this release fixes compatibility
with Git 1.7.
Unfortunately, we had to increase our minimum supported version of Git to
1.7.2, in order to get git status --porcelain
and orphan branches. Neither of
these are that big of a deal-breaker, so in theory we could support some
slightly older versions of git.
Full changelog below:
Continue reading Release v0.038...
A short release to potentially fix some possible installation problems, reported
by CPAN Testers.