Skip to content

feat: display changelog on webui #447

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
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

fritznastor
Copy link

-wrote a small script to always fetch the latest changelog
-also added an svg file for the changelog icon

@NicolasIRAGNE NicolasIRAGNE changed the title Display changelog webui feat: display changelog on webui Jul 24, 2025
@NicolasIRAGNE
Copy link
Contributor

aye that's pretty nice!
however I think

  1. fetching the latest always is not the best strategy (eg. if we push a release on github but we don't deploy it the changelog would be wrong)
  2. having the entire changelog with dates would be nice
  3. we need to be able to set which repo to pull the info from in case of fork / self host for example

but not 100% sure on how to achieve this, perhaps env var? I need to read up on how release please works

@fritznastor
Copy link
Author

@NicolasIRAGNE

Having the entire changelog with dates as in just having a separate pop up in the webui and not linking to the github?
Surely having it only pull info from the main should be fine, since every release comes with a changelog right?

@ix-56h
Copy link
Contributor

ix-56h commented Jul 25, 2025

Surely having it only pull info from the main should be fine, since every release comes with a changelog right?
It depends. We never know what can happen in the future.

So, redirecting to https://github.com/coderamp-labs/gitingest/releases is good enough.

@fritznastor
Copy link
Author

So, redirecting to https://github.com/coderamp-labs/gitingest/releases is good enough.

I simplified it so it just redirects to the link you put down.

@NicolasIRAGNE
Copy link
Contributor

Yeah still not sure about that because consider the following case:

  • we updated the repo with a new release (v0.3.0)
  • we did not update production environment yet so it is still on v0.2.0
  • clicking changelog shows you v0.3.0

but now that we have a proper changelog.md we can probs use this

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

Successfully merging this pull request may close these issues.

3 participants