You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, passing the link field to an entry in the releases list will override the default changelogTemplate link. However, for some projects there are blog posts that highlight some releases when they are particularly relevant, alongside (instead of replacing) the actual changelog. For example:
Describe the solution you'd like
It would be nice to have support for an additional field that would complement link instead of replacing it. It could be called e.g. announcementLink.
Describe alternatives you've considered
For now I settled on adding a comment in the yaml source to document the relevant link, but it would be nice if these links were properly exposed in the site, or at least in the API.
Additional context
I searched for additional issues but didn't find any related discussion.
Also, maybe it could be relevant to also have a further link field, for projects whose versions aren't immediately released as LTS but get promoted afterwards (e.g. Jenkins, Julia. Maybe ltsPromotionLink?
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, passing the
link
field to an entry in thereleases
list will override the defaultchangelogTemplate
link. However, for some projects there are blog posts that highlight some releases when they are particularly relevant, alongside (instead of replacing) the actual changelog. For example:Julia: Julia 1.11 Highlights (changelog), Julia 1.10 Highlights (changelog), Julia 1.9 Highlights (changelog)
Deno: Deno 1.0 (changelog), Announcing Deno 2 (changelog)
Git: Highlights from Git 2.48 (changelog)
Describe the solution you'd like
It would be nice to have support for an additional field that would complement
link
instead of replacing it. It could be called e.g.announcementLink
.Describe alternatives you've considered
For now I settled on adding a comment in the yaml source to document the relevant link, but it would be nice if these links were properly exposed in the site, or at least in the API.
Additional context
I searched for additional issues but didn't find any related discussion.
Also, maybe it could be relevant to also have a further link field, for projects whose versions aren't immediately released as LTS but get promoted afterwards (e.g. Jenkins, Julia. Maybe
ltsPromotionLink
?The text was updated successfully, but these errors were encountered: