Skip to content

[Feature]: A changelog (Low Priority) #465

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

Open
1 task done
UnchartedSystems opened this issue May 29, 2025 · 1 comment
Open
1 task done

[Feature]: A changelog (Low Priority) #465

UnchartedSystems opened this issue May 29, 2025 · 1 comment
Labels
enhancement New feature or request

Comments

@UnchartedSystems
Copy link

Feature Description

I'm coming back to Elpaca after ~6 months and I notice it's progressed from 0.8 -> 0.11. I'm curious what's changed and what known issues might be outstanding. I can't find this information through any of the links from the readme. A changelog, whether through github, or a simple text log within the repo, would be useful.

Confirmation

  • The feature I'm proposing does not already exist in Elpaca
@UnchartedSystems UnchartedSystems added the enhancement New feature or request label May 29, 2025
@progfolio
Copy link
Owner

progfolio commented May 29, 2025

elpaca-fetch elpaca should default to a commit log. I suggest pairing that with elpaca-log-update-mode for all packages. Some of the commit changes offer more technical details than would be found in a typical change log, but I usually include a broad summary for most changes. I'll see if I can come up with something that strikes a balance between a manually maintained changelog (not something I'm too keen on maintaining) and raw git output.

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

No branches or pull requests

2 participants