0.29.1

• Upgrades handlebars, improves warning #251

0.29.0

• #249 CI reporter output can now be configured to be saved to a file in application config (thanks @gruntruk!) (Docs)

0.28.3

• Upgrades grunt-asset-fingerprint to support CDN prefixes

0.28.2

• Adds support for .hbs extension in server-side templates in app/pages - Fixes #237 cc/ @krainboltgreene

0.28.1

• Upgrades jasmine-stealth (bug fix)

0.28.0

Warning: This release breaks backwards-compatibility for less users! If you use Lineman to compile less files, please read these notes.

We're currently working on slimming down the lineman npm package's dependencies to only what is really core to most web applications. This means that certain functionalities that have previously been built into every Lineman project will be extracted into Lineman plugins over the coming weeks. The first of these is lineman-less. Expect lineman-sass to come next. If you have feedback on this process, please feel free to pile-on in #193 or #201

Migrating your project to using lineman-less

If you use Less, please install lineman-less to continue compiling your less templates:

$ npm install --save-dev lineman-less

Note that going forward, Lineman will expect a single less file (by default, at app/css/main.less) to use the @import directive to require all other less files your project needs, whether they're located somewhere relative to app/css or vendor/css.

The reason for this particular change is that it's particularly bad form to naively concatenate a bunch of Less files and hope for the best. In fact, most people using Lineman and Less have been forced to override the (what could be fairly called "incorrect") default configuration for years now, and we think it's worth breaking backwards-compatibility to correct these defaults. If for some reason you need to rely on the old Less concatenation behavior, your options are to override the new defaults yourself or remain on a version of Lineman prior to 0.28.0 until you can override those defaults or migrate to the new non-concatenation style.

0.27.2

• Fixes API proxy 885545d

0.27.1

• Fixes relative url root when api proxying - #189

0.27.0

• #209 normalizes pkg config property (representing package.json) per npm's normalization rules (inserts defaults, expands strings to objects, etc). uses npm's own normalize-package-date. This means the pkg object will appear to lineman exactly as it appears to npm.
• lineman new now creates a more-valid package.json (description instead of title, no author.company)

0.26.0

• #221 - Adds a --process flag to the lineman config command that will interpolate grunt template values found in the config to show you the fields as grunt will use them.

From that commit:

The utility of the lineman config command is limited when the user
needs to see what the actual interpolated value will look like, esp.
for file expansions.

Example:

$ lineman config meta.banner
/*! <%= pkg.title || pkg.name %> - v<%= pkg.version %> - <%= grunt.template.today("yyyy-mm-dd") %> */

vs.

$ lineman config meta.banner --process
/*! An HTML/JS/CSS app - v0.0.1 - 2014-02-25 */