Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Latest release #91

Open
datapolitical opened this issue Apr 6, 2021 · 2 comments
Open

Use Latest release #91

datapolitical opened this issue Apr 6, 2021 · 2 comments

Comments

@datapolitical
Copy link

Is your feature request related to a problem? Please describe the problem you're trying to solve.

I'd like to specify to always use the latest tagged release of a theme. Right now I can only specify a particular release (v2.1.1) or just let it load the latest build, which is often broken.

Describe the solution you'd like

theme@latest would get the latest tagged release.

Describe alternatives you've considered

Updating the config file every time the theme version changes (which is a real pain)

@datapolitical
Copy link
Author

Bumping this

@parkr
Copy link

parkr commented Jul 23, 2021

@datapolitical Hey, the way this works for GitHub Actions is a good guide here. What they do, is they have @v2 as a branch, then merge changes into that branch and tag as they need to. So a tag/release v2.1.1 would be a specific SHA-1 on the v2 branch. Since jekyll-remote-theme will use any reference, I'd suggest using a latest branch here and merging changes into that branch in order to release!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants