jekyll/minima

Time for a new release

jekyllbot opened this issue ยท 20 comments

Hello, maintainers! ๐Ÿ‘‹

By my calculations, it's time for a new release of minima. It's been over 2 months since the last release, v2.5.1.

What else is left to be done before a new release can be made? Please make sure to update History.markdown too if it's not already updated.

Thanks! ๐Ÿ’ž โœจ

dgw commented

jekyllbot threatening to close its own issue for inactivity is pretty funny. ๐Ÿ˜ธ

But seriously, a new release with the color schemes (of particular interest to me) and other features added since 2.5.1 would be pretty great.

If anyone wants to play around with minima 3.0 it works with some minor coercion;

  1. Copy the following into your own project...
    • assets
    • _sass
    • _layouts
    • _includes
  2. bundle add jekyll-seo-tag
  3. remove theme: minima from _config.yml
dgw commented

You can use a newer version of minima as a gem theme like this (in Gemfile):
gem "minima", :github => 'jekyll/minima', :ref => 'd4bfaf2'

Indeed. By "play around with" i meant monkey around w/ the source.

You can use a newer version of minima as a gem theme like this (in Gemfile):
gem "minima", :github => 'jekyll/minima', :ref => 'd4bfaf2'

When using this line in my Gemfile, I get:

Using jekyll-watch 2.2.1
Fetching kramdown 1.17.0
Installing kramdown 1.17.0
Using liquid 4.0.3
Using mercenary 0.3.6
Using pathutil 0.16.2
Fetching rouge 3.20.0
Installing rouge 3.20.0
Using safe_yaml 1.0.5
Fetching jekyll 3.8.4
Installing jekyll 3.8.4
Using jekyll-feed 0.13.0
Using jekyll-seo-tag 2.6.1
Using minima 2.5.0 from https://github.com/jekyll/minima.git (at d4bfaf2@d4bfaf2)
Bundle complete! 4 Gemfile dependencies, 28 gems now installed.

And the version tagged 2.5.0 in git seems used instead of the commit specified. I think it is because the field spec.version in the file minima.gemspec has not been updated since 2.5.0.

When will another release happen? It's long overdue.

Another reason to add a release is that Github pages is still pinned to v2.5.1, which was released over a year ago.

Here's the github-pages gem: https://github.com/github/pages-gem/blob/master/lib/github-pages/plugins.rb#L52

Does this mean we cannot use the latest version of minima as a gem theme with GitHub Pages? (Without manually copying over the source.)

You can use the latest version of minima with GitHub Pages.
Just use the remote_theme feature:

# _config.yml

# Add to plugins: list
plugins:
  - jekyll-remote-theme

# set up remote_theme
remote_theme: jekyll/minima

@ashmaroli thank you! This worked nicely.

In addition, if you'd like to make sure that your site remains fixed at a particular commit of minima, you can specify the git ref

# set up remote_theme
remote_theme: jekyll/minima@3cdd14dff1216f561c68329e0b7420c2dc9b796a

+1 on this one. It would be great to cut a 3.0 release.

It's going to be 2 years now. What's stopping minima to get a new release? Default Jekyll installation still runs older minima theme.

If I am learning enough to get to this point in reviewing a repo to request a new release, you KNOW it's been awhile. lol.

Srsly tho, a new release would be welcomed; just sayin'

Lets say we decided to not release anymore gems off this repo..
Lets say we decided to have this be consumed only as a remote_theme or a theme via Bundler and Gemfile.

Lets say we have not taken any decisions whatsoever..
๐Ÿ˜ˆ

It seems half the time my site breaks on a push due to this. Anyone found a decent dark theme that is maintained worth migrating to?

Looks like Minima has been abandonded. Very sad. :(

Minima hasn't been abandoned. It's not ready for an official release. You're free to use the theme in current state via the jekyll-remote-theme plugin.

Who, either a person or an organization, has permission to publish a new release? Or does anyone know who actually owns this repo and can make a new release? The last release was in 2019, it is 2023 now.